Providing for mobility for flexible bandwidth carrier systems

ABSTRACT

Methods, systems, and devices for facilitating mobility between flexible bandwidth systems and other bandwidth systems are provided. These tools and techniques that provide mobility between different bandwidth systems may facilitate supporting circuit-switched (CS) services, such as CS voice services. Some embodiments provide for determining flexible bandwidth capable devices, such as user equipment. Some embodiments involve core network redirection where a core network may direct the handling of circuit-switched services when a flexible bandwidth system does not support the CS services. Some examples provide for radio access network determined handling of CS services when a flexible bandwidth system may not support the CS services. Some embodiments provide for transitioning to a flexible bandwidth system. Some embodiments provide for transitioning from flexible bandwidth systems to non-flexible bandwidth systems that have no support for some or all CS services, other flexible bandwidth systems, and/or systems that natively support CS voice services.

CROSS-RELATED APPLICATIONS

The present application for patent claims priority to ProvisionalApplication No. 61/568,742 entitled “SIGNAL CAPACITY BOOSTING,COORDINATED FORWARD LINK BLANKING AND POWER BOOSTING, AND REVERSE LINKTHROUGHPUT INCREASING FOR FLEXIBLE BANDWIDTH SYSTEMS” filed Dec. 9,2011, and assigned to the assignee hereof and hereby expresslyincorporated by reference herein for all purposes. The presentapplication for patent also claims priority to Provisional ApplicationNo. 61/621,904 entitled “PROVIDING FOR MOBILITY BETWEEN FLEXIBLEBANDWIDTH SYSTEMS AND NORMAL BANDWIDTH SYSTEMS” filed Apr. 9, 2012, andassigned to the assignee hereof and hereby expressly incorporated byreference herein for all purposes.

BACKGROUND

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be multiple-accesssystems capable of supporting communication with multiple users bysharing the available system resources (e.g., time, frequency, andpower). Examples of such multiple-access systems include code-divisionmultiple access (CDMA) systems, time-division multiple access (TDMA)systems, frequency-division multiple access (FDMA) systems, 3GPP LongTerm Evolution (LTE) systems, and orthogonal frequency-division multipleaccess (OFDMA) systems.

Service providers are typically allocated blocks of frequency spectrumfor exclusive use in certain geographic regions. These blocks offrequencies are generally assigned by regulators regardless of themultiple access technology being used. In most cases, these blocks arenot integer multiple of channel bandwidths, hence there may beunutilized parts of the spectrum. As the use of wireless devices hasincreased, the demand for and value of this spectrum has generallysurged, as well. Nonetheless, in some cases, wireless communicationssystems may not utilize portions of the allocated spectrum because theportions are not big enough to fit a standard or normal waveform. Thedevelopers of the LTE standard, for example, recognized the problem anddecided to support many different system bandwidths (e.g., 1.4, 3, 5,10, 15 and 20 MHz). This may provide one partial solution to theproblem. Flexible bandwidth systems may provide another solution, thoughsome flexible bandwidth systems may not support circuit-switchedservices.

SUMMARY

Methods, systems, and devices for facilitating mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. These tools and techniques that providemobility between different bandwidth systems may facilitate supportingcircuit-switched (CS) services, such as circuit-switched voice services.Some embodiments provide for determining flexible bandwidth capabledevices, such as user equipment (UE). Some embodiments involve corenetwork (CN) redirection, where a core network may direct the handlingof circuit-switched services, such as a CS voice service, when aflexible bandwidth system does not support the CS services. Someexamples provide for radio access network (RAN) directed and/ordetermined handling of CS services, such as CS voice services, when aflexible bandwidth system does not support the CS services. Someembodiments provide for transitioning or spring forward to a flexiblebandwidth system. Some embodiments provide for transitioning or fallbackfrom flexible bandwidth systems to non-flexible bandwidth systems thathave no support for some or all CS services (e.g., CS voice), otherflexible bandwidth systems, and/or systems that natively support CSvoice services.

Flexible bandwidth carriers for wireless communications systems mayutilize portions of spectrum that may not be big enough to fit a normalwaveform utilizing flexible bandwidth waveforms. A flexible bandwidthsystem that utilizes a flexible bandwidth carrier may be generated withrespect to a normal bandwidth system through dilating, or scaling down,the time or the chip rate of the flexible bandwidth system with respectto the normal bandwidth system. Some embodiments may increase thebandwidth of a waveform through expanding, or scaling up, the time orthe chip rate of the flexible bandwidth system.

Some embodiments include a method for providing mobility within wirelesscommunications systems. The method may include: identifying, at a corenetwork, a lack of support for one or more circuit-switched (CS)services on a flexible bandwidth radio access network from multipleradio access networks; and/or redirecting, at the core network, the oneor more CS services for a user equipment from the flexible bandwidthradio access network to a radio access network that supports thecircuit-switched service from the multiple radio access networks. Thecircuit-switched service may include a circuit-switched voice service.

Some embodiments include registering, at the core network, the userequipment over the flexible bandwidth radio access network with respectto at least one packet switched service. Some embodiments includeregistering, at the core network, the user equipment over the flexiblebandwidth radio access network with respect to at least onecircuit-switched service. The at least one circuit-switched service mayinclude a non-voice circuit switched service. The at least one non-voicecircuit-switched service may include at least SMS or CS data. Someembodiments include receiving, at the core network, a registrationrequest from the user equipment on the flexible bandwidth radio accessnetwork.

The one or more CS services may include at least a CS voice service, aRelease 99 CS voice service, or a CS voice service over one or more datachannels. The user equipment may be camped on the flexible bandwidthradio access network. The user equipment may be currently at least beingserved by or camped on a flexible bandwidth carrier that lacks supportfor a CS service. The CS service may be a CS voice service.

In some cases, the core network may be aware of the capabilities of theflexible bandwidth RAN. In some cases, the flexible bandwidth radioaccess network may aware that the flexible bandwidth radio accessnetwork lacks support for the circuit-switched service but does notinitiate redirection. In some cases, the core network may be unawarethat the CS service is unsupported on the flexible bandwidth radioaccess network. In some cases, the core network may determine that theCS service is unsupported on the flexible bandwidth radio accessnetwork.

Some embodiments include a wireless communications system configured formobility. The system may include: means for identifying, at a corenetwork, a lack of support for one or more circuit-switched (CS)services on a flexible bandwidth radio access network from multipleradio access networks; and/or means for redirecting, at the corenetwork, the one or more CS services for a user equipment from theflexible bandwidth radio access network to a radio access network thatsupports the circuit-switched service from the plurality of radio accessnetworks.

Some embodiments include means for registering, at the core network, theuser equipment over the flexible bandwidth radio access network withrespect to at least one packet switched service. Some embodimentsinclude means for registering, at the core network, the user equipmentover the flexible bandwidth radio access network with respect to atleast one circuit-switched service. Some embodiments include means forreceiving, at the core network, a registration request from the userequipment on the flexible bandwidth radio access network.

In some cases, the user equipment may be camped on the flexiblebandwidth radio access network. The user equipment may currently be atleast being served by or camped on a flexible bandwidth carrier thatlacks support for a CS service. In some cases, the circuit-switchedservice includes a circuit-switched voice service.

In some cases, the core network may be aware of the capabilities of theflexible bandwidth radio access network. In some cases, the flexiblebandwidth radio access network may be aware that the flexible bandwidthradio access network lacks support for the circuit-switched service butdoes not initiate redirection. In some cases, the core network may beunaware that the CS service is unsupported on the flexible bandwidthradio access network. In some cases, the core network may determine thatthe CS service is unsupported on the flexible bandwidth radio accessnetwork.

Some embodiments include a computer program product for mobility in awireless communications system that may include a non-transitorycomputer-readable medium that may include: code for identifying, at acore network, a lack of support for one or more circuit-switched (CS)services on a flexible bandwidth radio access network from multipleradio access networks; and code for redirecting, at the core network,the one or more CS services for a user equipment from the flexiblebandwidth radio access network to a radio access network that supportsthe circuit-switched service from the multiple radio access networks.

Some embodiments include code for registering, at the core network, theuser equipment over the flexible bandwidth radio access network withrespect to at least one packet switched service. Some embodimentsinclude code for registering, at the core network, the user equipmentover the flexible bandwidth radio access network with respect to atleast one circuit-switched service. Some embodiments include code forreceiving, at the core network, a registration request from the userequipment on the flexible bandwidth radio access network.

In some cases, the user equipment may be camped on the flexiblebandwidth radio access network. The user equipment may currently be atleast being served by or camped on a flexible bandwidth carrier thatlacks support for a CS service. In some cases, the circuit-switchedservice may include a circuit-switched voice service.

In some cases, the core network may be aware of the capabilities of theflexible bandwidth radio access network. In some cases, the flexiblebandwidth radio access network may be aware that the flexible bandwidthradio access network lacks support for the circuit-switched service butdoes not initiate redirection. In some cases, the core network may beunaware that the CS service may be unsupported on the flexible bandwidthradio access network. In some cases, the core network determines thatthe CS service is unsupported on the flexible bandwidth radio accessnetwork.

Some embodiments include a wireless communications device configured formobility in a wireless communications system. The device may include atleast one processor that may be configured to: identify, at a corenetwork, a lack of support for one or more circuit-switched (CS)services on a flexible bandwidth radio access network from multipleradio access networks; and/or redirect, by the core network, the one ormore CS services for a user equipment from the flexible bandwidth radioaccess network to a radio access network that supports thecircuit-switched service from the multiple radio access networks.

The at least one processor may be further configured to register, at thecore network, the user equipment over the flexible bandwidth radioaccess network with respect to at least one packet switched service. Theat least one processor may be further configured to register, at thecore network, the user equipment over the flexible bandwidth radioaccess network with respect to at least one circuit-switched service.The at least one processor may be further configured to: receive, at thecore network, a registration request from the user equipment on theflexible bandwidth radio access network.

In some cases, the user equipment may be camped on the flexiblebandwidth radio access network. In some cases, the user equipment maycurrently be at least being served by or camped on a flexible bandwidthcarrier that lacks support for a CS service. In some cases, thecircuit-switched service includes a circuit-switched voice service.

In some cases, the core network may be aware of the capabilities of theflexible bandwidth radio access network. In some cases, the flexiblebandwidth radio access network may be aware that the flexible bandwidthradio access network lacks support for the circuit-switched service butdoes not initiate redirection. In some cases, the core network may beunaware that the CS service is unsupported on the flexible bandwidthradio access network. In some cases, the core network may determine thatthe CS service is unsupported on the flexible bandwidth radio accessnetwork.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the spirit and scope of the appended claims. Features whichare believed to be characteristic of the concepts disclosed herein, bothas to their organization and method of operation, together withassociated advantages will be better understood from the followingdescription when considered in connection with the accompanying figures.Each of the figures is provided for the purpose of illustration anddescription only, and not as a definition of the limits of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the following drawings. In theappended figures, similar components or features may have the samereference label. Further, various components of the same type may bedistinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If only the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

FIG. 1 shows a block diagram of a wireless communications system inaccordance with various embodiments;

FIG. 2A shows an example of a wireless communications system where aflexible bandwidth waveform fits into a portion of spectrum not broadenough to fit a normal waveform in accordance with various embodiments;

FIG. 2B shows an example of a wireless communications system where aflexible bandwidth waveform fits into a portion of spectrum near an edgeof a band in accordance with various embodiments;

FIG. 2C shows an example of a wireless communications system where aflexible bandwidth waveform partially overlaps a normal waveform inaccordance with various embodiments;

FIG. 2D shows an example of a wireless communications system where aflexible bandwidth waveform is completely overlapped by a normalwaveform in accordance with various embodiments;

FIG. 2E shows an example of a wireless communications system where oneflexible bandwidth waveform is completely overlapped by a normalwaveform and another flexible bandwidth waveform partially overlaps anormal waveform in accordance with various embodiments;

FIG. 2F shows an example of a wireless communications system where onenormal waveform partially overlaps another normal waveform in accordancewith various embodiments;

FIG. 3A shows a block diagram of a wireless communications system inaccordance with various embodiments;

FIG. 3B shows a block diagram of a wireless communications system inaccordance with various embodiments;

FIG. 4 shows a call flow in accordance with various embodiments;

FIG. 5 shows a call flow in accordance with various embodiments;

FIG. 6 shows a block diagram of a device configured for user equipmentcapability identification in accordance with various embodiments.

FIG. 7 shows a communications system configured for user equipmentidentification in accordance with various embodiments;

FIG. 8 shows a block diagram of a user equipment configured for mobilityin accordance with various embodiments;

FIG. 9A shows a flow diagram of a method for determining flexiblebandwidth capable user equipment in accordance with various embodiments;

FIG. 9B shows a flow diagram of a method for determining flexiblebandwidth capable user equipment in accordance with various embodiments;

FIG. 9C shows a flow diagram of a method for determining flexiblebandwidth capable user equipment in accordance with various embodiments;

FIG. 10 shows a block diagram of a device that includes mobilityfunctionality in accordance with various embodiments;

FIG. 11 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 12A shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 12B shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 12C shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 13 shows a block diagram of a device that includes mobilityfunctionality in accordance with various embodiments;

FIG. 14 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 15A shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 15B shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 15C shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 16 shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 17 shows a block diagram of a device that includes mobilityfunctionality in accordance with various embodiments;

FIG. 18A shows a communications system in accordance with variousembodiments;

FIG. 18B shows a communications system in accordance with variousembodiments;

FIG. 18C shows a communications system in accordance with variousembodiments;

FIG. 19A shows a call flow in accordance with various embodiments;

FIG. 19B shows a call flow in accordance with various embodiments;

FIG. 20A shows a call flow in accordance with various embodiments;

FIG. 20B shows a call flow in accordance with various embodiments;

FIG. 21 shows a communications system in accordance with variousembodiments;

FIG. 22 shows a handover scenario table in accordance with variousembodiments;

FIG. 23A shows a call flow in accordance with various embodiments;

FIG. 23B shows a call flow in accordance with various embodiments;

FIG. 24A shows a call flow in accordance with various embodiments;

FIG. 24B shows a call flow in accordance with various embodiments;

FIG. 24C shows a call flow in accordance with various embodiments;

FIG. 24D shows a call flow in accordance with various embodiments;

FIG. 25 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 26 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 27 shows a block diagram of a user equipment configured formobility in accordance with various embodiments;

FIG. 28A shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 28B shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 28C shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 29 shows a block diagram of a device that includes mobilityfunctionality in accordance with various embodiments;

FIG. 30A shows a call flow in accordance with various embodiments;

FIG. 30B shows a call flow in accordance with various embodiments;

FIG. 31A shows a call flow in accordance with various embodiments;

FIG. 31B shows a call flow in accordance with various embodiments;

FIG. 32A shows a call flow in accordance with various embodiments;

FIG. 32B shows a call flow in accordance with various embodiments;

FIG. 33 shows a call flow in accordance with various embodiments;

FIG. 34 shows a call flow in accordance with various embodiments;

FIG. 35A shows a call flow in accordance with various embodiments;

FIG. 35B shows a call flow in accordance with various embodiments;

FIG. 36A shows a call flow in accordance with various embodiments;

FIG. 36B shows a call flow in accordance with various embodiments;

FIG. 36C shows a call flow in accordance with various embodiments;

FIG. 37A shows a call flow in accordance with various embodiments;

FIG. 37B shows a call flow in accordance with various embodiments;

FIG. 38 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 39 shows a block diagram of a communications system configured forproviding mobility for wireless communications systems in accordancewith various embodiments;

FIG. 40 shows a block diagram of a user equipment configured formobility in accordance with various embodiments;

FIG. 41A shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 41B shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 41C shows a flow diagram of a method for providing mobility withinwireless communications systems in accordance with various embodiments;

FIG. 42 shows a block diagram of a wireless communications system thatincludes a base station and a user equipment in accordance with variousembodiments.

DETAILED DESCRIPTION

Methods, systems, and devices for facilitating mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. These tools and techniques that providemobility between different bandwidth systems may facilitate supportingcircuit-switched (CS) services, such as circuit-switched voice services.Some embodiments provide for determining flexible bandwidth capabledevices, such as user equipment (UE). Some embodiments involve corenetwork (CN) redirection, where a core network may direct the handlingof circuit-switched services, such as a CS voice service, when aflexible bandwidth system does not support the CS services. Someexamples provide for radio access network (RAN) directed and/ordetermined handling of CS services, such as CS voice services, when aflexible bandwidth system does not support the CS services. Someembodiments provide for transitioning or spring forward to a flexiblebandwidth system. Some embodiments provide for transitioning or fallbackfrom flexible bandwidth systems to non-flexible bandwidth systems thathave no support for some or all CS services (e.g., CS voice), otherflexible bandwidth systems, and/or systems that natively support CSvoice services.

In addition to circuit-switched services, which may be typically carriedin UMTS over Release 99 channels for example, CS services can be carriedover high speed data channels (commonly known as CS over HS). For theformer, all communication path traversed by the voice signal may becircuit-switched, while for the latter, the radio access network aspect(communication path between the RNC and UE) may use data centric highspeed data channels (HSDPA, HSUPA channels). In CS over HS, the rest ofthe communication path may use the same resources as used in thestandard circuit-switched. Flexible bandwidth HSDPA and HSUPA networkscan be used to support CS over HS. Some flexible bandwidth systems maybe able to support certain CS services (e.g., voice) by one means (e.g.,Voice over HS) and not by another mean Release 99 CS voice. These twovoice services may be seen as one CS services or as two distinct CSservices.

Some embodiments provide for determining flexible bandwidth capabledevices, such as flexible bandwidth capable UEs. In some embodiments, aflexible bandwidth capable UE transmits messages indicating whether theUE supports flexible bandwidth. These messages may be in response toreceiving different messages from a radio access network, for example.Some embodiments allow for differentiating legacy UEs from flexiblebandwidth capable UEs through the different messages these different UEsmay or may not transmit in response to receiving different types ofmessages. For example, legacy UEs may transmit failure messages whenthey receive messages related to flexible bandwidth, while flexiblebandwidth capable UEs may respond differently, such as through notsending a failure message. Flexible bandwidth capable UEs may alsosupport normal bandwidth systems, such as normal bandwidth UMTS. Thesetools and techniques may allow a radio access network and/or corenetwork to determine which UEs have flexible bandwidth capabilities.

In some embodiments, a core network may direct the handling ofcircuit-switched services, such as a circuit-switched voice service,when a flexible bandwidth system does not support the CS services. Insome examples, a user equipment may be registered with both CS andpacket switched (PS) services on a flexible bandwidth radio accessnetwork. The core network may identify a lack of support for one or morecircuit-switched services on a flexible bandwidth system, and redirectthe circuit-switched service for the user equipment to a radio accessnetwork that supports the circuit-switched service.

Some embodiments provide for radio access network directed and/ordetermined handling of circuit-switched services, such as CS voiceservices, when a flexible bandwidth system does not support the CSservices. Embodiments may include: communicating with a user equipmentusing a flexible bandwidth radio access network from multiple radioaccess networks; and determining, by the flexible bandwidth radio accessnetwork, to redirect a circuit-switched service for the user equipmentto a radio access network that supports the circuit-switched servicefrom the multiple radio access networks.

Some embodiments provide for transitioning or spring forward to aflexible bandwidth system. Some embodiments may include transitioningfrom a first radio access network to a second radio access network,where the first radio access network includes a normal bandwidth radioaccess network and the second radio access network includes a flexiblebandwidth radio access network. Some embodiments include a method forfacilitating mobility to a flexible bandwidth system that may include:communicating over first radio access network, where the first radioaccess network utilizes a first bandwidth carrier; identifying a secondradio access network, where the second radio access network utilizes afirst flexible bandwidth carrier; and transitioning from utilizing thefirst bandwidth carrier of the first radio access network to utilizingthe first flexible bandwidth carrier of the second radio access network.The first bandwidth carrier may be a normal bandwidth carrier or asecond flexible bandwidth carrier different from the first flexiblebandwidth carrier.

Some embodiments provide for transitioning or fallback from flexiblebandwidth systems to non-flexible bandwidth systems that have no supportfor some or all CS services (e.g., CS voice), other flexible bandwidthsystems, and/or systems that natively support CS voice servicesincluding: transitioning from a first radio access network to secondradio access network, where the first radio access network includes aflexible bandwidth radio access network and the second radio accessnetwork includes a normal bandwidth radio access network or anotherflexible bandwidth system. In one example, a method for facilitatingmobility for wireless communications systems may include: communicatingover first radio access network, where the first radio access networkutilizes a first flexible bandwidth carrier; identifying a second radioaccess network, where the second radio access network utilizes a secondbandwidth carrier; and transitioning from utilizing the flexiblebandwidth carrier of the first radio access network to utilizing thesecond bandwidth carrier of the second radio access network. Thistransition may happen between different radio access technologies (RATs)(e.g., from Flexible bandwidth Universal Terrestrial Radio AccessNetwork (F-UTRAN) to GSM Radio Access Network (GERAN)) or between thesame RATs (e.g., from flexible bandwidth UTRAN to UTRAN). The secondbandwidth carrier may include a normal bandwidth carrier or anotherflexible bandwidth carrier different from the first bandwidth carrier.

Techniques described herein may be used for various wirelesscommunications systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA,Peer-to-Peer, and other systems. The terms “system” and “network” areoften used interchangeably. A CDMA system may implement a radiotechnology such as CDMA2000, Universal Terrestrial Radio Access (UTRA),etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000Releases 0 and A are commonly referred to as CDMA2000 1X, 1X, etc.IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High RatePacket Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and othervariants of CDMA. A TDMA system may implement a radio technology such asGlobal System for Mobile Communications (GSM). An OFDMA or OFDM systemmay implement a radio technology such as Ultra Mobile Broadband (UMB),Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal MobileTelecommunication System (UMTS). 3GPP Long Term Evolution (LTE) andLTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA,E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from anorganization named “3rd Generation Partnership Project” (3GPP). CDMA2000and UMB are described in documents from an organization named “3rdGeneration Partnership Project 2” (3GPP2). The techniques describedherein may be used for the systems and radio technologies mentionedabove, as well as other systems and radio technologies.

Thus, the following description provides examples, and is not limitingof the scope, applicability, or configuration set forth in the claims.Changes may be made in the function and arrangement of elementsdiscussed without departing from the spirit and scope of the disclosure.Various embodiments may omit, substitute, or add various procedures orcomponents as appropriate. For instance, the methods described may beperformed in an order different from that described, and various stepsmay be added, omitted, or combined. Also, features described withrespect to certain embodiments may be combined in other embodiments.

Referring first to FIG. 1, a block diagram illustrates an example of awireless communications system 100 in accordance with variousembodiments. The system 100 includes base stations 105, user equipment115, a base station controller 120, and a core network 130 (thecontroller 120 may be integrated into the core network 130 in someembodiments; in some embodiments, controller 120 may be integrated intobase stations 105). The system 100 may support operation on multiplecarriers (waveform signals of different frequencies). Multi-carriertransmitters can transmit modulated signals simultaneously on themultiple carriers. Each modulated signal may be a Code Division MultipleAccess (CDMA) signal, Time Division Multiple Access (TDMA) signal,Frequency Division Multiple Access (FDMA) signal, Orthogonal FDMA(OFDMA) signal, Single-Carrier FDMA (SC-FDMA) signal, etc. Eachmodulated signal may be sent on a different carrier and may carrycontrol information (e.g., pilot signals), overhead information, data,etc. The system 100 may be a multi-carrier LTE network capable ofefficiently allocating network resources.

The user equipment 115 may be any type of mobile station, userequipment, access terminal, subscriber unit, or user equipment. The userequipment 115 may include cellular phones and wireless communicationsdevices, but may also include personal digital assistants (PDAs),smartphones, other handheld devices, netbooks, notebook computers, etc.Thus, the term user equipment should be interpreted broadly hereinafter,including the claims, to include any type of wireless or mobilecommunications device.

Throughout this application, some user equipment may be referred to asflexible bandwidth capable user equipment, flexible bandwidth compatibleuser equipment, and/or flexible bandwidth user equipment. This maygenerally mean that the user equipment is flexible capable orcompatible. In general, these devices may also be capable of normalfunctionality with respect to one or more normal radio accesstechnologies (RATs). The use of the term flexible as meaning flexiblecapable or flexible compatible may generally be applicable to otheraspects of system 100, such as for controller 120 and/or base stations105, or a radio access network.

The base stations 105 may wirelessly communicate with the user equipment115 via a base station antenna. The base stations 105 may be configuredto communicate with the user equipment 115 under the control of thecontroller 120 via multiple carriers. Each of the base station 105 sitescan provide communication coverage for a respective geographic area. Insome embodiments, base stations 105 may be referred to as a NodeB,eNodeB, Home NodeB, and/or Home eNodeB. The coverage area for each basestation 105 here is identified as 110-a, 110-b, or 110-c. The coveragearea for a base station may be divided into sectors (not shown, butmaking up only a portion of the coverage area). The system 100 mayinclude base stations 105 of different types (e.g., macro, micro, femto,and/or pico base stations).

The different aspects of system 100, such as the user equipment 115, thebase stations 105, the core network 130, and/or the controller 120 maybe configured to utilize flexible bandwidth and waveforms in accordancewith various embodiments. System 100, for example, shows transmissions125 between user equipment 115 and base stations 105. The transmissions125 may include uplink and/or reverse link transmission, from a userequipment 115 to a base station 105, and/or downlink and/or forward linktransmissions, from a base station 105 to a user equipment 115. Thetransmissions 125 may include flexible and/or normal waveforms. Normalwaveforms may also be referred to as legacy and/or normal waveforms.

The different aspects of system 100, such as the user equipment 115, thebase stations 105, the core network 130, and/or the controller 120 maybe configured to utilize flexible bandwidth and waveforms in accordancewith various embodiments. For example, different aspects of system 100may utilize portions of spectrum that may not be big enough to fit anormal waveform. Devices such as the user equipment 115, the basestations 105, the core network 130, and/or the controller 120 may beconfigured to adapt the chip rates, spreading factor, and/or scalingfactors to generate and/or utilize flexible bandwidth and/or waveforms.Some aspects of system 100 may form a flexible subsystem (such ascertain user equipment 115 and/or base stations 105) that may begenerated with respect to a normal subsystem (that may be implementedusing other user equipment 115 and/or base stations 105) throughdilating, or scaling down, the time of the flexible subsystem withrespect to the time of the normal subsystem.

In some embodiments, different aspects of system 100, such as the userequipment 115, the base stations 105, the core network 130, and/or thecontroller 120 may be configured for mobility between flexible bandwidthsystems and other bandwidth systems, such as normal bandwidth systemsand/or other flexible bandwidth systems. Different aspects of system100, such as the user equipment 115, the base stations 105, the corenetwork 130, and/or the controller 120, may be configured to providemobility between different bandwidth systems may facilitate supportingcircuit-switched services, such as circuit-switched voice services.Different aspects of system 100, such as the user equipment 115, thebase stations 105, the core network 130, and/or the controller 120, maybe configured to provide for determining flexible bandwidth capabledevices, such as user equipment 115. Some embodiments involve corenetwork redirection, where core network 130 may direct the handling ofcircuit-switched services, such as a CS voice service, when a flexiblebandwidth system does not support the CS services. Different aspects ofsystem 100, such as the user equipment 115, the base stations 105, thecore network 130, and/or the controller 120, may be configured toprovide for radio access network, which may include base stations 105and/or controller 120, directed and/or determined handling of CSservices, such as CS voice services, when a flexible bandwidth systemdoes not support the CS services. Different aspects of system 100, suchas the user equipment 115, the base stations 105, the core network 130,and/or the controller 120, may be configured to provide fortransitioning or spring forward to a flexible bandwidth system.Different aspects of system 100, such as the user equipment 115, thebase stations 105, the core network 130, and/or the controller 120, maybe configured to provide for transitioning or fallback from flexiblebandwidth systems to non-flexible bandwidth systems that have no supportfor some or all CS services (e.g., CS voice), other flexible bandwidthsystems, and/or systems that natively support CS voice services.

FIG. 2A shows an example of a wireless communications system 200-a witha base station 105-a and a user equipment 115-a in accordance withvarious embodiments, where a flexible bandwidth waveform 210-a fits intoa portion of spectrum not broad enough to fit a normal waveform 220-a.System 200-a may be an example of system 100 of FIG. 1. In someembodiments, the flexible bandwidth waveform 210-a may overlap with thenormal waveform 220-a that either the base 105-a and/or the userequipment 115-a may transmit. In some cases, the normal waveform 220-amay completely overlap the flexible bandwidth waveform 210-a. Someembodiments may also utilize multiple flexible bandwidth waveforms 210.In some embodiments, another base station and/or user equipment (notshown) may transmit the normal waveform 220-a and/or the flexiblebandwidth waveform 210-a. FIG. 2B shows an example of a wirelesscommunications system 200-b with a base station 105-b and user equipment115-b, where a flexible bandwidth waveform 210-b fits into a portion ofspectrum near an edge of a band, which may be a guard band, where normalwaveform 220-b may not fit. System 200-b may be an example of system 100of FIG. 1. User equipment 115-a/115-b and/or base stations 105-a/105-bmay be configured to dynamically adjust the bandwidth of the flexiblebandwidth waveforms 210-a/210-b in accordance with various embodiments.

FIG. 2C shows an example of a wireless communications system 200-c wherea flexible bandwidth waveform 210-c partially overlaps a normal waveform220-c in accordance with various embodiments. System 200-c may be anexample of system 100 of FIG. 1. FIG. 2D shows an example of a wirelesscommunications systems 200-d where a flexible bandwidth waveform 210-dis completely overlapped by a normal waveform 220-d in accordance withvarious embodiments. System 200-d may be an example of system 100 ofFIG. 1. FIG. 2E shows an example of a wireless communications system200-e where one flexible bandwidth waveform 210-f is completelyoverlapped by a normal waveform 220-e and another flexible bandwidthwaveform 210-e partially overlaps the normal waveform 220-e inaccordance with various embodiments. System 200-e may be an example ofsystem 100 of FIG. 1. FIG. 2F shows an example of a wirelesscommunications system 200-f where one normal waveform 220-f partiallyoverlaps another normal waveform 220-g in accordance with variousembodiments. System 200-f may be an example of system 100 of FIG. 1.Systems 200-c, 200-d, 200-e, and/or 200-f may be configured such thatthe bandwidth of the flexible bandwidth waveforms 210-c, 210-d, and/or210-e may be dynamically adjusted in accordance with variousembodiments.

In general, a first waveform or carrier bandwidth and a second waveformor carrier bandwidth may partially overlap when they overlap by at least1%, 2%, and/or 5%. In some embodiments, partial overlap may occur whenthe overlap is at least 10%. In some embodiments, the partial overlapmay be less than 99%, 98%, and/or 95%. In some embodiments, the overlapmay be less than 90%. In some cases, a flexible bandwidth waveform orcarrier bandwidth may be contained completely within another waveform orcarrier bandwidth such as seen in system 200-d of FIG. 2. This overlapstill reflects partial overlap, as the two waveforms or carrierbandwidths do not completely coincide. In general, partial overlap canmean that the two or more waveforms or carrier bandwidths do notcompletely coincide (i.e., the carrier bandwidths are not the same).

Some embodiments may utilize different definitions of overlap based onpower spectrum density (PSD). For example, one definition of overlapbased on PSD is shown in the following overlap equation for a firstcarrier:

${overlap} = {100\%*{\frac{\int_{0}^{\infty}{P\; S\; {D_{1}(f)}*P\; S\; {D_{2}(f)}}}{\int_{0}^{\infty}{P\; S\; {D_{1}(f)}*P\; S\; {D_{1}(f)}}}.}}$

In this equation, PSD₁(f) is the PSD for a first waveform or carrierbandwidth and PSD₂(f) is the PSD for a second waveform or carrierbandwidth. When the two waveforms or carrier bandwidths coincide, thenthe overlap equation may equal 100%. When the first waveform or carrierbandwidth and the second waveform or carrier bandwidth at leastpartially overlap, then the overlap equation may not equal 100%. Forexample, the Overlap Equation may result in a partial overlap of greaterthan or equal to 1%, 2%, 5%, and/or 10% in some embodiments. The overlapequation may result in a partial overlap of less than or equal to 99%,98%, 95%, and/or 90% in some embodiments. One may note that in the casein which the first waveform or carrier bandwidth is a normal waveform orcarrier bandwidth and the second waveform or a carrier waveform is aflexible bandwidth waveform or carrier bandwidth that is containedwithin the normal bandwidth or carrier bandwidth, then the overlapequation may represent the ratio of the flexible bandwidth compared tothe normal bandwidth, written as a percentage. Furthermore, the overlapequation may depend on which carrier bandwidth's perspective the overlapequation is formulated with respect to. Some embodiments may utilizeother definitions of overlap. In some cases, another overlap may bedefined utilizing a square root operation such as the following:

${overlap} = {100\%*{\sqrt{\frac{\int_{0}^{\infty}{P\; S\; {D_{1}(f)}*P\; S\; {D_{2}(f)}}}{\int_{0}^{\infty}{P\; S\; {D_{1}(f)}*P\; S\; {D_{1}(f)}}}}.}}$

Other embodiments may utilize other overlap equations that may accountfor multiple overlapping carriers.

FIG. 3A shows a wireless communications system 300-a with a base station105-c and user equipment 115-c and 115 d, in accordance with variousembodiments. Different aspects of system 300-a, such as the userequipment 115-c and/or 115-d and/or the base stations 105-c, may beconfigured for mobility between flexible bandwidth systems and otherbandwidth systems, such as normal bandwidth systems and/or otherflexible bandwidth systems. Different aspects of system 300-a, such asthe user equipment 115-c and/or 115-d and/or the base stations 105-c,may be configured to provide mobility between different bandwidthsystems may facilitate supporting circuit-switched services, such ascircuit-switched voice services. Different aspects of system 300-a, suchas the user equipment 115-c and/or 115-d and/or the base stations 105-c,may be configured to provide for determining flexible bandwidth capabledevices, such as user equipment 115-c and/or 115-d. Some embodimentsinvolve core network redirection, where a core network may direct thehandling of circuit-switched services, such as a CS voice service, whena flexible bandwidth system does not support the CS services. Differentaspects of system 300-a, such as the user equipment 115-c and/or 115-dand/or the base stations 105-c, may be configured to provide for radioaccess network, which may include base stations 105-c, directed and/ordetermined handling of CS services, such as CS voice services, when aflexible bandwidth system does not support the CS services. Differentaspects of system 300-a, such as the user equipment 115-c and/or 115-dand/or the base stations 105-c, may be configured to provide fortransitioning or spring forward to a flexible bandwidth system.Different aspects of system 300-a, such as the user equipment 115-cand/or 115-d and/or the base stations 105-c, may be configured toprovide for transitioning or fallback from flexible bandwidth systems tonon-flexible bandwidth systems that have no support for some or all CSservices (e.g., CS voice), other flexible bandwidth systems, and/orsystems that natively support CS voice services.

Transmissions 305-a and/or 305-b between the user equipment 115-c/115-dand the base station 105-a may utilize flexible bandwidth waveforms thatmay be generated to occupy less (or more) bandwidth than a normalwaveform. For example, at a band edge, there may not be enough availablespectrum to place a normal waveform. For a flexible bandwidth waveform,as time gets dilated, the frequency occupied by a waveform goes down,thus making it possible to fit a flexible bandwidth waveform intospectrum that may not be broad enough to fit a normal waveform. In someembodiments, the flexible bandwidth waveform may be scaled utilizing ascaling factor N with respect to a normal waveform. Scaling factor N maytake on numerous different values including, but not limited to, integervalues such as 1, 2, 3, 4, 8, etc. N, however, does not have to be aninteger.

Some embodiments may utilize additional terminology. A new unit D may beutilized. The unit D is dilated. The unit is unitless and has the valueof N. One can talk about time in the flexible system in terms of“dilated time”. For example, a slot of say 10 ms in normal time may berepresented as 10 Dms in flexible time (note: even in normal time, thiswill hold true since N=1 in normal time: D has a value of 1, so 10Dms=10 ms). In time scaling, one can replace most “seconds” with“dilated-seconds”. Note frequency in Hertz is 1/s.

As discussed above, a flexible bandwidth waveform may be a waveform thatoccupies less bandwidth than a normal waveform. Thus, in a flexiblebandwidth system, the same number of symbols and bits may be transmittedover a longer duration compared to normal bandwidth system. This mayresult in time stretching, whereby slot duration, frame duration, etc.,may increase by a scaling factor N. Scaling factor N may represent theratio of the normal bandwidth to flexible bandwidth (BW). Thus, datarate in a flexible bandwidth system may equal (Normal Rater 1/N), anddelay may equal (Normal Delay×N). In general, a flexible systems channelBW=channel BW of normal systems/N. Delay×BW may remain unchanged.Furthermore, in some embodiments, a flexible bandwidth waveform may be awaveform that occupies more bandwidth than a normal waveform.

Throughout this specification, the term normal system, subsystem, and/orwaveform may be utilized to refer to systems, subsystems, and/orwaveforms that involve embodiments that may utilize a scaling factorthat may be equal to one (e.g., N=1) or a normal or standard chip rate.These normal systems, subsystems, and/or waveforms may also be referredto as standard and/or legacy systems, subsystems, and/or waveforms.Furthermore, flexible systems, subsystems, and/or waveforms may beutilized to refer to systems, subsystems, and/or waveforms that involveembodiments that may utilize a scaling factor that may be not equal toone (e.g., N=2, 4, 8, ½, ¼, etc.). For N>1, or if a chip rate isdecreased, the bandwidth of a waveform may decrease. Some embodimentsmay utilize scaling factors or chip rates that increase the bandwidth.For example, if N<1, or if the chip rate is increased, then a waveformmay be expanded to cover bandwidth larger than a normal waveform.Flexible systems, subsystems, and/or waveforms may also be referred toas fractional systems, subsystems, and/or waveforms in some cases.Fractional systems, subsystems, and/or waveforms may or may not changebandwidth, for example. A fractional system, subsystem, or waveform maybe flexible because it may offer more possibilities than a normal orstandard system, subsystem, or waveform (e.g., N=1 system). Furthermore,the use of the term flexible may also be utilized to mean flexiblebandwidth capable.

Referring next to FIG. 3B, a block diagram illustrates an example of awireless communications system 300-b. The system 300-b may be an exampleof the system 100 described with reference to FIG. 1. NodeBs 105 andradio network controllers (RNCs) 120 are parts of wirelesscommunications system 300-b. In the illustrated example, the systemincludes a UMTS Terrestrial Radio Access Network (UTRAN) 121-a and aflexible UMTS (F-UMTS) 121-b (or, in general, UTRAN 121). A UTRAN 121may be a collective term for the NodeBs 105 (or base stations) and thecontrol equipment for the NodeBs 105 (or RNC 120) it contains which makeup the UMTS radio access network. This may be a 3 G communicationsnetwork which can carry both real-time circuit switched and IP-basedpacket-switched traffic types. The UTRAN 121 may provide an airinterface access method for the user equipment (UE) 115-e Connectivityis provided between the UE 115-e and the core network 130-a by the UTRAN121-a and/or F-UTRAN 121-b. The UTRAN 121 may transport data packets tomultiple UEs 115-e

The UTRANs 121 may be connected internally or externally to otherfunctional entities by a number of interfaces. UTRANs 121 may be incommunication with a core network 130-a via external interface supportedby RNCs 120. In addition, the RNCs 120 manage a set of base stationscalled NodeBs 105. RNCs 120 may be in communication with each other, aswell. UTRANs 121 may be largely autonomous from the core network 130-abecause the RNCs 120 may be interconnected. The NodeBs 105 may be inwireless communication with the UE 115-e. The system may be furtherconnected to additional networks (not shown), such as a corporateintranet, the Internet, or a conventional public switched telephonenetwork, and may transport data packets between each UE 115-e and suchoutside networks.

Each RNC 120 may fill multiple roles. First, they may control theadmission of new UEs 115-e or services attempting to use the NodeB 105.Second, from the NodeB 105, or base station, point of view, the RNC 120may be a controlling RNC 120. Controlling admission ensures that UEs115-e may be allocated radio resources (bandwidth and signal/noiseratio) up to what the network has available. An RNC 120 may terminatethe UE's 115-e link layer communications.

For an air interface, UMTS often uses a wideband spread-spectrum mobileair interface known as Wideband Code Division Multiple Access (orW-CDMA). W-CDMA uses a direct sequence code division multiple accesssignaling method (or CDMA) to separate users. W-CDMA is a thirdgeneration standard for mobile communications. W-CDMA evolved from GSM(Global System for Mobile Communications)/GPRS a second generationstandard, which is oriented to voice communications with limited datacapability. The first commercial deployments of W-CDMA are based on aversion of the standards called W-CDMA Release 99. The air interface mayalso be configured to utilize flexible bandwidth.

The different aspects of system 300-b, such as the user equipment 115-e,the base stations 105-e, the core network 130-a, RNC 120-b, and/orF-UTRAN 121-b may be configured to utilize flexible bandwidth andwaveforms in accordance with various embodiments. For example, differentaspects of system 300-b may utilize portions of spectrum that may not bebig enough to fit a normal waveform. Devices such as the user equipment115, the base stations 105, the core network 130, and/or the controller12, such as the user equipment 115-e, the base stations 105-e, the corenetwork 130-a, RNC 120-b, and/or F-UTRAN 121-b may be configured toadapt the chip rates, spreading factor, and/or scaling factors togenerate and/or utilize flexible bandwidth bandwidth and/or waveforms.Some aspects of system 300-b may form a flexible bandwidth subsystem(such as certain user equipment 115 and/or base stations 105) that maybe generated with respect to a normal subsystem (that may be implementedusing other user equipment 115 and/or base stations 105) throughdilating, or scaling down, the time of the flexible bandwidth subsystemwith respect to the time of the normal subsystem.

In some embodiments, different aspects of system 300-b, such as the userequipment 115-e, the base stations 105-e, the core network 130-a, RNC120-b, and/or F-UTRAN 121-b, may be configured for mobility betweenflexible bandwidth systems and other bandwidth systems, such as normalbandwidth systems and/or other flexible bandwidth systems. Differentaspects of system 300-b, such as the user equipment 115-e, the basestations 105-e, the core network 130-a, RNC 120-b, and/or F-UTRAN 121-b,may be configured to provide mobility between different bandwidthsystems may facilitate supporting circuit-switched services, such ascircuit-switched voice services. Different aspects of system 300-b, suchas the user equipment 115-e, the base stations 105-e, the core network130-a, RNC 120-b, and/or F-UTRAN 121-b, may be configured to provide fordetermining flexible bandwidth capable devices, such as user equipment115-e. Some embodiments involve core network redirection, where corenetwork 130-a may direct the handling of circuit-switched services, suchas a CS voice service, when a flexible bandwidth system does not supportthe CS services. Different aspects of system 300-b, such as the userequipment 115-e, the base stations 105-e, the core network 130-a, RNC120-b, and/or F-UTRAN 121-b, may be configured to provide for radioaccess network, which may include UTRAN 121-a and/or F-UTRAN 1210-b,directed and/or determined handling of CS services, such as CS voiceservices, when a flexible bandwidth system does not support the CSservices. Different aspects of system 300-b, such as the user equipment115-e, the base stations 105-e, the core network 130-a, RNC 120-b,and/or F-UTRAN 121-b, may be configured to provide for transitioning orspring forward to a flexible bandwidth system. Different aspects ofsystem 300-b, such as the user equipment 115-e, the base stations 105-e,the core network 130-a, RNC 120-b, and/or F-UTRAN 121-b, may beconfigured to provide for transitioning or fallback from flexiblebandwidth systems to non-flexible bandwidth systems that have no supportfor some or all CS services (e.g., CS voice), other flexible bandwidthsystems, and/or systems that natively support CS voice services.

Methods, systems, and devices for mobility between flexible bandwidthsystems and normal bandwidth systems are provided. Some embodimentsprovide for flexible-capable user equipment to be registered with aflexible bandwidth system and/or normal bandwidth system based on theservices the user equipment may utilize. For example, a user equipmentmay be registered with a normal bandwidth system that may supportcircuit-switched voice services that the flexible bandwidth system maynot support, while other service, such as packet-switched services, andpossibly some circuit-switched services, may be provided through theflexible bandwidth system. Some embodiments may involve situations wherea core network may or may not be aware of the flexible-capabilities ofthe user equipment or other aspects of the wireless communicationssystems, such as a flexible-capable radio access network (RAN). Someembodiments may provide for a core network and/or RAN to redirectcircuit-switched voice services or other services to different networksbased on capability and/or usage. Furthermore, some embodiments may beconfigured to provide for transitioning, or fallback, from a flexiblebandwidth system to a normal bandwidth system. Some embodiments mayprovide for transitioning, or spring forward, from a normal bandwidthsystem to a flexible bandwidth system.

For some flexible bandwidth systems, supporting voice may presentdifferent issues. For example, a data rate for voice may get reducedand/or additional delay may get introduced. Some embodiments may addresssuch issues without utilizing native voice support in a flexiblebandwidth system, such as a flexible bandwidth UTRAN. Some embodimentsmay include transitioning and/or fallback to other RATs (e.g., GERAN,UTRAN, CDMA 1x) for circuit-switched voice. To address such issues,mobility between flexible bandwidth systems, such as flexible bandwidthUTRAN, and non-flexible bandwidth systems or systems that nativelysupport CS voice (e.g., GERAN/UTRAN (for voice fallback)) and other wayround (for PS connection transfer either for better coverage or higherrate) may be supported.

In the following, fractional bandwidth RAN, flexible bandwidth RAN,fractional bandwidth UTRAN, and/or flexible bandwidth UTRAN may mean thesame. In general, this terminology refers to flexible bandwidth RadioAccess Network that may include an RNC and Node B modified to supportflexible bandwidth functionality, such as flexible bandwidth UMTSfunctionalities. Some embodiments may provide mobility in accordancewith various embodiments through several core network based embodiments.These embodiments maybe related to the behavior of the core network.

In some embodiments, Location Area (LA) and/or Routing Area (RA) forflexible bandwidth UMTS, UMTS, and GSM, for example, may be overlappingbut not necessarily the same as the cell sizes are different. Theflexible bandwidth UMTS and UMTS and/or GSM cells may overlap partiallyor completely. In some embodiments, SGSN and MSC serving UMTS, GSM andflexible bandwidth UMTS networks are the same. This may be the case, forexample, when UMTS, GSM, and flexible bandwidth UMTS are deployed at thesame site. In some embodiments, flexible bandwidth UTRAN supports CS SMSand other CS services except CS voice call. For CS voice, it may supportsome CS voice related signaling (e.g., Paging Type 2 message for MT CSvoice call when UE is in PS call.

Some embodiment may handle situations where there is no CS support onthe flexible bandwidth RAN, such as a flexible bandwidth UTRAN. In someembodiments, the CN is aware that flexible bandwidth UTRAN does notoffer CS services. Mobiles may do combined IMSI/GPRS Attach, forexample. Redirection by CN and/or flexible bandwidth UTRAN may be used.

Some embodiment may handle situations where there is CS without voicesupport on a flexible bandwidth RAN, such as a flexible bandwidth UTRAN.For example, a flexible bandwidth UTRAN may support CS signaling (e.g.,Paging Type 2 message for MT CS voice call when UE is in PS call) andmight or might not support SMS and CS data services but does not supportCS voice call. The CN may or may not be aware of this lack of voicesupport. UEs may do combined IMSI/GPRS Attach. For embodiments with CNaware, redirection by CN or flexible bandwidth UTRAN may be used. Forembodiments with CN unaware, redirection by flexible bandwidth UTRAN maybe utilized. In some embodiments, the CN may ensure that the UE isregistered with the appropriate MSC and SGSN. MSC and SGSN might supportdifferent RATs.

The following describes some embodiments where there may be no CSsupport on a flexible bandwidth RAN, such as a flexible bandwidth UTRAN.Merely by way of example, a UE may be camping on the flexible bandwidthUTRAN. The UE may participate in a CS+PS registration process, such as acombined GPRS and IMSI (CS+PS) Attach on the flexible bandwidth UTRAN.In some embodiments, the GPRS Attach is received by the SGSN and the UEis registered on the PS domain at the SGSN. In some embodiments, the CNis aware of lack of CS support on flexible bandwidth UTRAN, and as aresult, the IMSI attach may be forwarded to MSC/VLR of the GSM/UMTSnetwork with overlapping routing and location areas as the flexiblebandwidth UTRAN routing areas. RAN changes and CN changes may beinvolved in some embodiments. In these embodiments, CN redirection orRAN redirection may both work.

The following description includes numerous call flows, including thoseshown in FIGS. 4, 5, 19, 20, 22-24, and 30-37. These call flows andother portions may include different mobile originated (MO) (i.e., userequipment originated) and/or mobile terminated (MT) (i.e., userequipment terminated) communications in some cases. These call flows andother portions may show or refer to user equipment (UE), flexiblebandwidth radio access network (flexible bandwidth RAN), WCDMA UniversalTerrestrial Radio Access Network (UTRAN), GSM/EDGE Radio Access Network(GERAN), UMTS UTRAN, Flexible bandwidth UMTS, combined Radio NetworkController (RNC), flexible bandwidth UTRAN, Mobile Switching Center(MSC), Visitor Location Register (VLR), Serving General Packet RadioService Support Node (SGSN), and/or Home Location Register (HLR). Ingeneral, a UE may in be implemented as generally described with respectto user equipment 115 throughout this application. Flexible bandwidthRAN, WCDMA UTRAN, GERAN, UMTS UTRAN, Flexible bandwidth UMTS, and/orcombined Radio Network Controller may be implemented as part of theradio access networks 121 as generally described throughout thisapplication. Mobile Switching Center (MSC), Visitor Location Register(VLR), Serving General Packet Radio Service Support Node (SGSN), and/orHome Location Register (HLR) may be implemented as part of the corenetworks 130 as generally described throughout this application.

For example, turning to FIG. 4, a call flow 400 is shown involvingregistration for the UE when there may not be CS support on the flexiblebandwidth UTRAN in accordance with various embodiments. In call flow400, GPRS Attach may be performed with SGSN. HLR may provide informationto the SGSN to assist it in finding the appropriate MSC. IMSI Attach maybe forwarded to MSC/VLR supporting UMTS/GSM network with overlappingLAs/RAs as the flexible bandwidth UMTS RAs. In this example, LAL and RAIin the “Attach accept” message may belong to different networks.Although not shown in the FIG. 4, authentication and security commandsmay typically be exchanged between the UE and CN network before the“Attach Accept” is sent to the UE.

Some embodiments include a flexible bandwidth system where CS signalingmay be supported by a flexible bandwidth RAN, but no voice support onthe flexible bandwidth RAN, such as a flexible bandwidth UTRAN. Merelyby way of example, a UE may be camping on the flexible bandwidth UTRAN.The UE may perform a combined IMSI and GPRS Attach on the flexiblebandwidth UTRAN. In some embodiments, the CN is aware that some CSsignaling and maybe some services (e.g., SMS, CS Data etc.) aresupported on flexible bandwidth UTRAN, but not voice. The CN mayregister the UE for CS′ and PS calls (where CS′ means all CS servicesexcept CS voice) on flexible bandwidth UTRAN and CS voice on another RANthat may support voice, such as UMTS or GSM. MT/MO CS (except voice) andPS calls may be handled on flexible bandwidth UTRAN. When MT CSnotification is received at the MSC connected to UMTS or GSM, a page maybe forwarded to the UE through the MSC supporting non-voice CS or theSGSN (for flexible bandwidth UTRAN) and UE may be redirected to anotherCS voice support system, such as GSM or UMTS. CN redirection and/or RANredirection may both works. RAN changes and/or CN changes may beimplemented in some cases.

Merely by way of example, a UE may be camping on the flexible bandwidthUTRAN. The UE may perform a combined IMSI and GPRS Attach on theflexible bandwidth UTRAN. In some embodiments, the CN is not aware thatflexible bandwidth UTRAN does not support voice services, so it mayregister the UE for CS+PS calls on flexible bandwidth UTRAN. MT/MO CS(except voice) and PS calls may be handled on flexible bandwidth UTRAN.When MT CS notification is received at the MSC, a page may be sent tothe UE and UE may redirected to another voice-support network, such asGSM or UMTS. In some embodiments, RAN redirection is utilized. RANchanges may occur in some embodiments.

FIG. 5 shows an example of a call flow 500 for a registration process inaccordance with various embodiments where they may be PS and some CSsupport on the flexible bandwidth RAN. The HLR may provide informationto the SGSN to assist it in finding the appropriate MSC. IMSI Attach maybe forwarded to MSC/VLR supporting flexible bandwidth UTRAN. LAI and RAIin the “Attach Accept” message may belong to the flexible bandwidthUTRAN. Although, it is not shown in the FIG. 5, authentication andsecurity commands may be typically exchanged between the UE and CNnetwork before the “Attach Accept” is sent to the UE.

Methods, systems, and devices for identifying flexible bandwidth capabledevices are provided. These methods, systems, and/or devices may includedevice 600 of FIG. 6, RAN 121 of FIG. 7, UE 115 of FIG. 8, method 900-aof FIG. 9A, method 900-b of FIG. 9B, and/or method 900-c of FIG. 9C, forexample. Some embodiments provide for determining flexible bandwidthcapable devices, such as user equipment (UE). In some embodiments, aflexible bandwidth capable UE transmits messages indicating whether theUE supports flexible bandwidth radio access network. These messages maybe in response to receiving different messages from a radio accessnetwork, for example. Some embodiments allow for differentiating legacyUEs from flexible bandwidth capable UEs through the different messagesthese different UEs may or may not transmit in response to receivingdifferent types of messages. For example, legacy UEs may transmitfailure messages when they receive messages related to flexiblebandwidth radio access networks, while flexible bandwidth capable UEsmay respond differently, such as through not sending a failure message.Flexible bandwidth capable UEs may also support normal bandwidthsystems, such as normal bandwidth UMTS. These tools and techniques mayallow a radio access network and/or core network to determine which UEshave flexible bandwidth capabilities.

Some embodiments include identifying flexible bandwidth UEs through astandardized solution. The UTRAN may send an “UE Capability Enquiry”message to connected mode flexible bandwidth UMTS and normal UMTS UEswhile they are in connected mode on a normal bandwidth UMTS carrier. TheUE capability enquiry can be used to request the UE to transmit itscapability information related to any radio access network that issupported by the UE. The UEs may respond back with the “UE capabilityinformation” message which states whether the UE supports flexiblebandwidth UMTS cells and in which frequency bands. The UTRAN may use themessage to determine which UEs to request inter-frequency measurementsfrom where the target carrier is flexible bandwidth UMTS carrier.

A flexible-compatible (or capable) UTRAN (which may support both normaland flexible bandwidth carriers) may infer the UE's flexible bandwidthcapability based on configuring measurement reports as the UE capabilitymay not indicate support of flexible bandwidth UMTS system in currentUMTS releases. Some embodiments provide for a flexible-bandwidthcompatible UTRAN (e.g., supports both normal and flexible bandwidthcarriers) that may know whether a UE is flexible bandwidth compatible ornot in other ways. In some cases, if a UE is asked to make a measurementthat is not supported by the UE, it may ignore the entire MeasurementControl Message and may send a Measurement Control Failure message tothe UTRAN with “failure cause” set to “unsupported measurement”. The UEmay continue with any ongoing processes and procedures as if theMeasurement Control Message has not been received. Some embodiments mayaddress this through the following procedure. In a step A, a flexiblebandwidth compatible UTRAN (supports normal+flexible bandwidth UMTSfrequencies) may send a Measurement Control Message corresponding tomeasurement in a chosen invalid UARFCN—a frequency which a legacy UE(that may not support flexible bandwidth UTMS) would consider as invalidbecause it is in band edge. In a step B, a legacy UE may send MeasureControl Failure Message as the measurement is not supported. On theother hand, a flexible bandwidth compatible UE may interpret the invalidUARFCN differently and may not send Measurement Control Failure Message.The flexible bandwidth-compatible UE may not send any MeasurementControl Failure message and might or might not send any MeasurementReport Message. Thus, cost to legacy UE may be the Measurement ControlMessage transmission from network with invalid UARFCN that triggers theMeasurement Control Failure Message from legacy UE. In a step C,flexible bandwidth-compatible UTRAN may know which UEs are flexiblebandwidth compatible from step B (i.e., UEs that have not sentMeasurement Control Failure Message). It may ask flexiblebandwidth-compatible UEs to go and make measurements on flexiblebandwidth UMTS frequencies and schedule Compressed Mode gaps. A variantmay be possible in which the invalid UARFCN may encode the flexiblebandwidth UMTS frequency, and possibly the bandwidth, eliminating step Cfor flexible bandwidth compatible UEs. Irrespective of the variants, theflexible bandwidth capable UE may send Measurement Report Message basedon whether flexible bandwidth UMTS carrier was detected.

Some embodiments may use some reserved bits in existing IEs (InformationElements) for a flexible bandwidth UMTS compatible UE to indicate itsflexible capability to a network that is flexible bandwidth UMTScapable. The reserved bits maybe ignored by a legacy network that is notflexible bandwidth capable. A flexible bandwidth UMTScompatible UE maysignal its capability using non-critical extension Information Elements(IE). In both cases, if a legacy RAN receives the IE, it may discard itwhile a flexible-compatible UMTS RAN may act upon this capabilityinformation. There may be also UTRAN Classmark Info sent by the UE.These could also be used by flexible-compatible UMTS UE to indicate itsflexible bandwidth capability and for flexible bandwidth UTRAN to knowthe UE's flexible bandwidth capabilities when there may befields/Information Elements to indicate such capability.

In some embodiments, there is measurement capability to indicatecapability for FDD measurements, 3.84 Mcps TDD measurements, 7.68 McpsTDD measurements, 1.28 Mcps TDD measurements, etc. In some embodiments,there is also measurement capability extension. Flexible bandwidth UMTScapability of UE can be indicated as another capability in themeasurement capability or measurement capability extension. Withflexible bandwidth UMTS being considered as same RAT as UMTS, andconsidering it as a UMTS “feature or special category”, an additional IEmay be added to the “UE radio access capability” or “UE radio accesscapability extension,” for example. In the extension, features such asdual cell capability, frequency band specific capability may bespecified. As an alternative, flexible bandwidth UMTS capability of UEcan be specified in “UE multi-mode/multi-RAT capability,” for example.This may cover both cases where flexible bandwidth UMTS is considered asmode of the same RAT (UMTS) or considered as a different RAT than UMTS.

Some embodiments provide for identifying UEs with flexible bandwidthcapabilities in other ways. For example, the network scheduledcompressed mode gaps for flexible UMTS and normal UMTS connected modeUEs may be utilized to search for neighboring cells on flexiblebandwidth UMTS carriers and determining the flexible bandwidth UMTScapability of UEs. Periodic reporting may be used to monitor if the UEcan identify neighboring ells on flexible bandwidth UMTS carriers withina given period of time. If neighboring cells on flexible bandwidth UMTScarriers may not be identified, the RAN may disable the inter-frequencymeasurements and the RAN may infer those UEs as normal or legacy UEsthat are not flexible bandwidth capable. For flexible bandwidth UMTScapable UEs that may identify neighboring cells on flexible bandwidthUMTS carriers, the reporting can be switched to event-based reportingand the RAN may infer these UEs as flexible bandwidth capable UEs.Inter-frequency handover may be triggered once a suitable event isreported to the UTRAN by the flexible bandwidth capable UE. The RAN mayalso choose to trigger an inter-frequency blind handover before the UEreports a suitable event.

Turning next to FIG. 6, a block diagram illustrates a device 600configured for user equipment identification in accordance with variousembodiments. The device 600 may be an example of aspects of the radioaccess networks 121 of FIG. 3B and/or FIG. 7; and/or user equipment 115of FIG. 1, FIG. 2, FIG. 3, FIG. 7, and/or FIG. 8. The device 600 mayalso be a processor. The device 600 may include a receiver module 605, aUE capability identification module 615, and/or a transmitter module620. Each of these components may be in communication with each other.

These components of the device 600 may, individually or collectively, beimplemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

The receiver module 605 may receive information such as packet, data,and/or signaling information regarding what device 600 has received ortransmitted. The received information may be utilized by the UEcapability identification module 615 for a variety of purposes.

In some embodiments, UE capability identification module 615 isconfigured for determining flexible bandwidth capable user equipment. UEcapability identification module 615 may be configured for: transmittingone or more messages to one or more user equipments (UEs), where the oneor more messages are configured to facilitate determining which of theone or more UEs is capable of utilizing a flexible bandwidth carrier;receiving one or more responses from one or more of the one or more UEsin response to the one or more transmitted messages; and/or utilizingthe one or more received responses to determine which of the one or moreUEs is capable of utilizing the flexible bandwidth carrier. In somecases, receiver module 605 and/or transmitter module 620 may beconfigured to perform one or more of these aspects.

In some cases, transmitting the one or more messages to one or more UEsutilizing device 600 may occur over another bandwidth carrier, which mayinclude a normal bandwidth carrier. The other bandwidth carrier may beon another radio access technology. Transmitting the one or moremessages to one or more UEs may occur over a first carrier that may besupported by all the UEs. Some embodiments include transmitting the oneor more messages over a first carrier to facilitate determining whichUEs are capable of supporting a second carrier, where the second carrieris a flexible bandwidth carrier. Transmitting the one or more messagesto one or more UEs may include transmitting a message to the one or moreUEs corresponding to a measurement for an unused frequency with respectto a normal bandwidth system. The unused frequency may include aninvalid frequency and or a conditional frequency.

Receiving the one or more responses from one or more of the UEsutilizing device 600 may include receiving one or more failures messagesfrom one or more of the one or more UEs reflecting that the UEs is notcapable of utilizing with respect to at least one flexible bandwidthcarrier. Receiving the one or more responses from one or more of the UEsmay include receiving one or more responses indicating the one or moreof the one or more UEs can identify flexible bandwidth carriers.Receiving the one or more response from one or more of the UEs mayinclude receiving one or more Information Elements (IEs) indicating theflexible bandwidth capabilities of one or more of the one or more UEs.Some embodiments include determining that a timing out period hasoccurred for at least one of the UEs.

Some embodiments of device 600 may provide for identifying UEcapabilities. For example, in some embodiments, the network issuescompressed mode gaps for flexible bandwidth UMTS and normal UMTSconnected mode UEs to search for neighboring cells on flexible bandwidthUMTS carriers. Periodic reporting may be used to monitor if the UE canidentify neighboring cells on Flexible bandwidth UMTS carriers after agiven period of time. If neighboring cells on flexible bandwidth UMTScarriers may not be identified, the RAN may disable the inter-frequencymeasurements. For flexible bandwidth UMTS UEs that may identifyneighboring cells on flexible bandwidth UMTS carriers, the reporting canbe switched to event-based reporting. Inter-frequency handover may betriggered once an event is reported to the flexible bandwidth compatibleUTRAN. The RAN may choose to trigger an inter-frequency handover beforethe UE reports an event.

In some embodiments, identifying UE capabilities may include astandardized solution. The UTRAN may issue an “UE capability Enquiry”message to connected mode flexible bandwidth UMTS and normal UMTS UEs.The UEs may respond back with the “UE capability information” messagewhich states whether the UE supports flexible bandwidth UMTS carriersand in which frequency bands. The UTRAN may use the message to determinefrom which UEs to request inter-frequency measurements for flexiblebandwidth UMTS carriers. In some embodiments, a flexiblebandwidth-compatible (or capable) UTRAN (supports both normal andflexible bandwidth carriers) may infer the UE's flexible bandwidthcapability based on configuring measurement reports as the UE capabilitymay not indicate support of flexible bandwidth UMTS. Some embodimentsmay use some reserved bits in existing IEs (Information Elements) thatmay not be processed by any network for a flexible bandwidth UMTScompatible UE to indicate its flexible bandwidth capability to network.In some embodiments, a flexible bandwidth UMTS-compatible UE may signalits capability using non-critical extension Information Elements (IE).In some embodiments, a flexible-compatible UE or network may use theadditional range in the IE that is not currently used. In some cases, ifa legacy RAN receives the IE, it may discard it while a flexiblebandwidth-compatible UTRAN may act upon this capability information.There may be also UTRAN Classmark Info sent by the UE. These could alsobe used by flexible bandwidth UMTS-compatible UE to indicate itsflexible bandwidth capability and for flexible bandwidth UTRAN to knowthe UE's flexible bandwidth capabilities when there may befields/Information Elements to indicate such capability.

In some embodiments, there is measurement capability to indicatecapability for FDD measurements, 3.84 Mcps TDD measurements, 7.68 McpsTDD measurements, 1.28 Mcps TDD measurements, etc. In some embodiments,there is also measurement capability extension. Flexible bandwidth-UMTScapability of UE can be indicated as another capability in themeasurement capability or measurement capability extension. Withflexible bandwidth UMTS as same RAT as UMTS and considering it a UMTS“feature or special category”, an additional IE may be added to the “UEradio access capability” or “UE radio access capability extension,” forexample. In the extension, features such as dual cell capability,frequency band specific capability may be specified. As an alternative,flexible bandwidth UMTS capability of UE can be specified in “UEmulti-mode/multi-RAT capability,” for example. This may cover both caseswhere flexible bandwidth UMTS is considered as mode of the same RAT(UMTS) or considered as a different RAT than UMTS.

Some embodiments may provide for a flexible-bandwidth compatible UTRAN(supports both normal and flexible bandwidth carriers) that may knowwhether a UE is flexible bandwidth compatible or not in other ways. Insome cases, if a UE may be asked to make a measurement that is notsupported by the UE, it may ignore the entire Measurement Commandmessage and may send a Measurement Control Failure message to the UTRANwith “failure cause” set to “unsupported measurement”. The UE maycontinue with any ongoing processes and procedures as if the MeasurementControl Message has not been received. Some embodiments may address thisthrough the following procedure. In a step A, a flexible compatibleUTRAN (supports normal and flexible bandwidth UMTS frequencies) may senda Measurement Control Message corresponding to measurement in a choseninvalid UARFCN—a frequency which a normal UE would consider as invalidbecause it is in band edge. In a step B, a legacy UE may send MeasureControl Failure Message as the measurement is not supported. On theother hand, a flexible bandwidth-compatible UE may interpret the invalidUARFCN differently and may not send Measurement Control Failure Message.The flexible bandwidth-compatible UE may not send any MeasurementControl Failure message and might or might not send any MeasurementReport Message. Thus, cost to legacy UE may be the Measurement ControlMessage transmission from network with invalid UARFCN that triggers theMeasurement Control Failure Message from the legacy UEs. In a step C,flexible bandwidth-compatible UTRAN may know which UEs are flexiblebandwidth compatible from through step B. It may ask flexiblebandwidth-compatible UEs to go and make measurements on flexiblebandwidth UMTS frequencies and turn on Compressed Mode gaps. A variantmay be possible in which the invalid UARFCN may encode the flexiblebandwidth UMTS frequency, and possibly the bandwidth, eliminating step Cfor flexible bandwidth compatible UEs. Irrespective of the variants, theflexible bandwidth capable UE may send Measurement Report Message basedon whether flexible bandwidth UMTS carrier was detected.

FIG. 7 shows a block diagram of a communications system 700 that may beconfigured for determining flexible bandwidth capable user equipment inaccordance with various embodiments. This system 700 may be an exampleof aspects of the system 100 depicted in FIG. 1, systems 200 of FIG. 2,systems 300 of FIG. 3, and/or system 4200 of FIG. 42; and/or device 600of FIG. 6. The radio access network 121-c may include aspects of a basestation 105 and/or a controller 120 to represent a combined systemand/or separate components that may comprise part of a radio accessnetwork. The radio access network 121-c may include antennas 745, atransceiver module 750, memory 770, and a processor module 765, whicheach may be in communication, directly or indirectly, with each other(e.g., over one or more buses). The transceiver module 750 may beconfigured to communicate bi-directionally, via the antennas 745, withthe user equipment 115-f, which may be a multi-mode user equipment. Thetransceiver module 750 (and/or other components of the radio accessnetwork 121-c) may also be configured to communicate bi-directionallywith one or more networks. In some cases, the radio access network 121-cmay communicate with the core network 130-b through networkcommunications module 775. Radio access network 121-c may include aneNodeB base station, a Home eNodeB base station, a NodeB base station,and/or a Home NodeB base station.

Radio access network 121-c may also communicate with other base stations105, such as base station 105-m and base station 105-n. Each of the basestations 105 may communicate with user equipment 115-f using differentwireless communications technologies, such as different Radio AccessTechnologies. In some cases, radio access network 121-c may communicatewith base stations such as 105-m and/or 105-n utilizing base stationcommunication module 720. In some embodiments, base stationcommunication module 720 may provide an X2 interface within an LTEwireless communication technology to provide communication between someof the base stations 105. In some embodiments, radio access network121-c may communicate with other base stations through core network130-b.

The memory 770 may include random access memory (RAM) and read-onlymemory (ROM). The memory 770 may also store computer-readable,computer-executable software code 771 containing instructions that areconfigured to, when executed, cause the processor module 765 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 771 maynot be directly executable by the processor module 765 but be configuredto cause the computer, e.g., when compiled and executed, to performfunctions described herein.

The processor module 765 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 765 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets to the transceiver module750, and provide indications of whether a user is speaking.Alternatively, an encoder may only provide packets to the transceivermodule 750, with the provision or withholding/suppression of the packetitself providing the indication of whether a user is speaking.

The transceiver module 750 may include a modem configured to modulatethe packets and provide the modulated packets to the antennas 745 fortransmission, and to demodulate packets received from the antennas 745.While some examples of the radio access network 121-c may include asingle antenna 745, the radio access network 121-c preferably includesmultiple antennas 745 for multiple links which may support carrieraggregation. For example, one or more links may be used to support macrocommunications with user equipment 115-f.

According to the architecture of FIG. 7, the radio access network 121-cmay further include a communications management module 730. Thecommunications management module 730 may manage communications withother base stations 105. By way of example, the communicationsmanagement module 730 may be a component of the radio access network121-c in communication with some or all of the other components of theradio access network 121-c via a bus. Alternatively, functionality ofthe communications management module 730 may be implemented as acomponent of the transceiver module 750, as a computer program product,and/or as one or more controller elements of the processor module 765.

The components for radio access network 121-c may be configured toimplement aspects discussed above with respect to device 600 of FIG. 6and may not be repeated here for the sake of brevity. The UEidentification module 615-a may be an example of the UE identificationmodule 615 of FIG. 6. UE identification module 615-a may include aflexible bandwidth UE identification module 711, a legacy UEidentification module 712, and/or a UE messaging module 713.

The radio access network 121-c may also include a spectrumidentification module 715. The spectrum identification module 715 may beutilized to identify spectrum available for flexible bandwidthwaveforms. In some embodiments, a handover module 725 may be utilized toperform handover procedures of the user equipment 115-f from one basestation 105 to another. For example, the handover module 725 may performa handover procedure of the user equipment 115-f from radio accessnetwork 121-c to another where normal waveforms are utilized between theuser equipment 115-f and one of the base stations and flexible bandwidthwaveforms are utilized between the user equipment and another basestation. A scaling module 727 may be utilized to scale and/or alter chiprates to generate flexible bandwidth waveforms.

In some embodiments, the transceiver module 750 in conjunction withantennas 745, along with other possible components of radio accessnetwork 121-c, may transmit information regarding flexible bandwidthwaveforms and/or scaling factors from the radio access network 121-c tothe user equipment 115-f, to other base stations 105-m/105-n, or corenetwork 130-b. In some embodiments, the transceiver module 750 inconjunction with antennas 745, along with other possible components ofradio access network 121-c, may transmit information to the userequipment 115-f, to other base stations 105-m/105-n, or core network130-b, such as flexible bandwidth waveforms and/or scaling factors, suchthat these devices or systems may utilize flexible bandwidth waveforms.

FIG. 8 is a block diagram 800 of a user equipment 115-g configured formobility in accordance with various embodiments. The user equipment115-g may have any of various configurations, such as personal computers(e.g., laptop computers, netbook computers, tablet computers, etc.),cellular telephones, PDAs, digital video recorders (DVRs), internetappliances, gaming consoles, e-readers, etc. The user equipment 115-gmay have an internal power supply (not shown), such as a small battery,to facilitate mobile operation. In some embodiments, the user equipment115-g may be the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 7,and/or FIG. 42, and/or the device 600 of FIG. 6. The user equipment115-g may be a multi-mode user equipment. The user equipment 115-g maybe referred to as a wireless communications device in some cases.

The user equipment 115-g may include antennas 840, a transceiver module850, memory 880, and a processor module 870, which each may be incommunication, directly or indirectly, with each other (e.g., via one ormore buses). The transceiver module 850 is configured to communicatebi-directionally, via the antennas 840 and/or one or more wired orwireless links, with one or more networks, as described above. Forexample, the transceiver module 850 may be configured to communicatebi-directionally with base stations 105 of FIG. 1, FIG. 2, FIG. 3A, FIG.42; and/or the radio access networks 121 of FIG. 3B and/or FIG. 7. Thetransceiver module 850 may include a modem configured to modulate thepackets and provide the modulated packets to the antennas 840 fortransmission, and to demodulate packets received from the antennas 840.While the user equipment 115-g may include a single antenna, the userequipment 115-g will typically include multiple antennas 840 formultiple links.

The memory 880 may include random access memory (RAM) and read-onlymemory (ROM). The memory 880 may store computer-readable,computer-executable software code 885 containing instructions that areconfigured to, when executed, cause the processor module 870 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 885 maynot be directly executable by the processor module 870 but be configuredto cause the computer (e.g., when compiled and executed) to performfunctions described herein.

The processor module 870 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 870 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 30 ms in length) representative ofthe received audio, provide the audio packets to the transceiver module850, and provide indications of whether a user is speaking.Alternatively, an encoder may only provide packets to the transceivermodule 850, with the provision or withholding/suppression of the packetitself providing the indication of whether a user is speaking.

According to the architecture of FIG. 8, the user equipment 115-g mayfurther include a communications management module 860. Thecommunications management module 860 may manage communications withother user equipment 115. By way of example, the communicationsmanagement module 860 may be a component of the user equipment 115-g incommunication with some or all of the other components of the userequipment 115-g via a bus. Alternatively, functionality of thecommunications management module 860 may be implemented as a componentof the transceiver module 850, as a computer program product, and/or asone or more controller elements of the processor module 870.

The components for user equipment 115-g may be configured to facilitatethe UE identification provided by device 600 of FIG. 6. For example,user equipment 115-g may have a RAN capability module 811 to provideinformation regarding the UE to convey specific RAN capabilityinformation to the RAN. User equipment 812 may include measurementmodule 812 that may also provide measurements that may allow a RAN todetermine whether the user equipment 115-g has flexible bandwidthcapabilities or may be a legacy UE.

The user equipment 115-g may also include a spectrum identificationmodule 815. The spectrum identification module 815 may be utilized toidentify spectrum available for flexible bandwidth waveforms. In someembodiments, a handover module 825 may be utilized to perform handoverprocedures of the user equipment 115-g from one base station to another.For example, the handover module 825 may perform a handover procedure ofthe user equipment 115-g from one base station to another where normalwaveforms are utilized between the user equipment 115-g and one of thebase stations and flexible bandwidth waveforms are utilized between theuser equipment and another base station. A scaling module 827 may beutilized to scale and/or alter chip rates to generate flexible bandwidthwaveforms.

In some embodiments, the transceiver module 850, in conjunction withantennas 840, along with other possible components of user equipment115-g, may transmit information regarding flexible bandwidth waveformsand/or scaling factors from the user equipment 115-g to base stations ora core network. In some embodiments, the transceiver module 850, inconjunction with antennas 840, along with other possible components ofuser equipment 115-g, may transmit information, such flexible bandwidthwaveforms and/or scaling factors, to base stations or a core networksuch that these devices or systems may utilize flexible bandwidthwaveforms.

Turning to FIG. 9A, a flow diagram of a method 900-a for determiningflexible bandwidth capable user equipment is provided in accordance withvarious embodiments. Method 900-a may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1 and/or FIG. 3B; the basestations 105 of FIG. 1, FIG. 2, FIG. 3A, FIG. 7, and/or FIG. 42; theuser equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 7, FIG. 8, and/orFIG. 42; the controllers 120 of FIG. 1 and/or FIG. 3B; the radio accessnetworks 121 of FIG. 3B and/or FIG. 7; and/or device 600 of FIG. 6.

At block 905, one or more messages may be transmitted to one or moreuser equipments (UEs). The one or more messages may be configured tofacilitate determining which of the one or more UEs is capable ofutilizing a flexible bandwidth carrier. At block 910, one or moreresponses may be received from one or more of the one or more UEs inresponse to the one or more transmitted messages. At block 915, the oneor more received responses may be utilized to determine which of the oneor more UEs is capable of utilizing the flexible bandwidth carrier.

Transmitting the one or more messages to one or more UEs may occur overa another bandwidth carrier, which may include a normal bandwidthcarrier. The other bandwidth carrier may be on another radio accesstechnology. Transmitting the one or more messages to one or more UEs mayoccur over a first carrier that may be supported by other UEs. Someembodiments include transmitting the one or more messages over a firstcarrier to facilitate determining which UEs are capable of supporting asecond carrier, where the second carrier is a flexible bandwidthcarrier. Transmitting the one or more messages to one or more UEs mayinclude transmitting a message to the one or more UEs corresponding to ameasurement for an unused frequency with respect to a normal bandwidthsystem. The unused frequency may include an invalid frequency and/or aconditional frequency.

Receiving the one or more responses from one or more of the one or moreUEs may include receiving one or more failures messages from one or moreof the one or more UEs reflecting that the UEs is not capable ofutilizing at least one flexible bandwidth carrier. Receiving the one ormore responses from one or more of the one or more UEs may includereceiving one or more responses indicating the one or more of the one ormore UEs can identify flexible bandwidth carriers. Receiving the one ormore response from one or more of the one or more UEs may includereceiving one or more Information Elements (IEs) indicating the flexiblebandwidth capabilities of one or more of the one or more UEs. Someembodiments include determining that a timing out period has occurredfor at least one of the UEs.

Turning to FIG. 9B, a flow diagram of a method 900-b for determiningflexible bandwidth capable user equipment is provided in accordance withvarious embodiments. Method 900-b may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1 and/or FIG. 3B; the basestations 105 of FIG. 1, FIG. 2, FIG. 3A, FIG. 7, and/or FIG. 42; theuser equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 7, FIG. 8, and/orFIG. 42; the controllers 120 of FIG. 1 and/or FIG. 3B; the radio accessnetworks 121 of FIG. 3B and/or FIG. 7; and/or device 600 of FIG. 6.Method 900-b may include one or more aspects of method 900-a of FIG. 9A.

At block 905-a, a Measurement Control Message corresponding to aninter-frequency measurement for a flexible bandwidth carrier may betransmitted to one or more UEs. At block 910-a, one or more MeasurementReport Messages may be received from one or more of the one or more UEs.At block 915-a, it may be determined which of the one or more UEs hasflexible bandwidth capabilities or not based on the one or more receivedmessages. At block 920, one or more UEs determined to have flexiblebandwidth capabilities may be directed to make one or more measurementswith respect to the flexible bandwidth carrier.

Turning to FIG. 9C, a flow diagram of a method 900-c for determiningflexible bandwidth capable user equipment is provided in accordance withvarious embodiments. Method 900-c may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1 and/or FIG. 3B; the basestations 105 of FIG. 1, FIG. 2, FIG. 3A, FIG. 7, and/or FIG. 42; theuser equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 7, FIG. 8, and/orFIG. 42; the controllers 120 of FIG. 1 and/or FIG. 3B; the radio accessnetworks 121 of FIG. 3B and/or FIG. 7; and/or device 600 of FIG. 6.Method 900-c may include one or more aspects of method 900-a of FIG. 9Aand/or method 900-b of FIG. 9B.

At block 905-b, one or more messages may be transmitted to one or moreUEs to facilitate determine UEs with flexible bandwidth capabilities. Atblock 910-b, one or more responses may be received from one or more ofthe one or more UEs. A UE with flexible bandwidth capabilities mayindicate its flexible bandwidth capabilities utilize InformationElements. At block 915-b, the flexible bandwidth capabilities of one ormore UEs may be determined based on the received Information Elements.

Methods, systems, and devices for providing mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. These methods, systems, and/or devicesmay include device 1000 of FIG. 10, core network 130-c of FIG. 11,method 1200-a of FIG. 12A, method 1200-b of FIG. 12B, and/or method 1600of FIG. 16. In some examples, a user equipment may be registered withboth CS and packet switched (PS) services on flexible bandwidth radioaccess network. In some examples, a core network (CN) may direct thehandling of circuit-switched (CS) services, such as a circuit-switchedvoice service, when a flexible bandwidth system does not support the anyor some of CS services (e.g., voice, SMS, etc.). A CN may choose someservices and not others, in some cases. Though the example of thecircuit switch services may include voices, other CS service may beredirected. The core network may identify a lack of support (forexample, from the UE registration) for a circuit-switched service on aflexible bandwidth carrier on which the flexible bandwidth capable UEcurrently is and redirect the user equipment to a radio access networkthat supports the circuit-switched service.

In some embodiments, the UE may register for a packet switched servicewith the CN through the flexible bandwidth radio access network. Also,through the flexible bandwidth radio access network, the UE may alsoregister for non-voice circuit-switched service with the CN. To startthe registration procedure, the UE may send a combined CS and PS attachrequest to the CN through the flexible bandwidth radio access network.The request may be received by the CN entity (e.g., SGSN) that providesPS domain services support for the flexible bandwidth RAN. The PS CN mayregister the UE for PS services and then may forward the CS attach tothe CS CN entity, the CN entity providing CS domain services support fora radio access network that supports CS services. In some embodiments,the core network may register the user equipment for a packet switchedservice over flexible bandwidth radio access network. In some otherembodiment, the core network may register the user equipment fornon-voice circuit-switched service over flexible bandwidth radio accessnetwork.

In some embodiments, the CS CN entity and PS CN entity may supportmultiple RAN. In some embodiments, Location Area (LA) and/or RoutingArea (RA) for flexible bandwidth UMTS, UMTS, and GSM, for example, maybe overlapping but not necessarily the same as the cell sizes may bedifferent. The flexible bandwidth UMTS and UMTS and/or GSM cells mayoverlap partially or completely. The SGSN and MSC serving UMTS, GSM andflexible UMTS networks may be the same. This may be the case, forexample, when UMTS, GSM, and flexible bandwidth UMTS may be deployed atthe same site. In some embodiments, flexible UTRAN support CS SMS andother CS services except CS voice call. For CS voice, it may supportsome CS voice related signaling (e.g., Paging Type 2 message for MT CSvoice call when user equipment is in PS call. UMTS may include bothWCDMA and/or HSPA, for example.

Some embodiments may handle situations where there is no CS support onthe flexible RAN, such as a flexible UTRAN. Some embodiment may handlesituations where support for some CS services may exist on the flexibleRAN, such as a flexible UTRAN. An example may be where CS voice on WCDMAis not supported, but CS SMSM or CS over HS is supported. The CN may beaware that the flexible UTRAN does not support all CS services. UEs mayperform a combined IMSI and GPRS Attach to register for both PS and CSservices with the CN through the flexible bandwidth RAN. In the casethat a CS service that is not supported by the flexible RAN is receivedand/or initiated while the UE is on the flexible bandwidth RAN, the CNmay redirect the call to another RAN that supports those services.

In some embodiments, the flexible RAN (e.g., flexible UTRAN) may supportCS services without voice. For example, a flexible UTRAN may support CSsignaling (e.g., Paging Type 2 message for MT CS voice call when userequipment is in PS call) and might or might not support SMS and CS dataservices but does not support CS voice call. The CN may be aware of thislack of voice support. When the CN is aware, redirection by CN orflexible UTRAN to UTRAN or any radio access network that supports CSvoice may be used when there is a CS voice call for the flexiblebandwidth capable UE on the flexible UTRAN. During the registration, theUE may register for CS and PS services with the MSC and SGSN that maysupport the flexible bandwidth RAN, other RANs that support CS voice,and/or other RATs.

The following describes some embodiments where there may be limited CSsupport (including no CS support) on a flexible RAN, such as a flexibleUTRAN. Other scenarios include scenarios where CS support may exist forsome CS services but not for all CS services. Furthermore, somescenarios include scenarios where a certain CS service may be supportedand for one reason or another, however, there may be advantages forthose services for the user equipment to be provided in another radioaccess network.

Some embodiments include a flexible bandwidth system where CS signalingmay be supported by a flexible RAN, but there may be no voice support onthe flexible RAN, such as a flexible UTRAN. In these cases, CNredirection may be utilized when the CN is aware that the flexiblebandwidth RAN does not support voice services. For example, a userequipment camping on the flexible UTRAN may perform a combined IMSI andGPRS Attach with the MSC and SGSN using the flexible UTRAN. The CN maybe aware that some CS signaling and maybe some services (e.g., SMS, CSData etc.) are supported on flexible UTRAN, but not CS voice. The CN mayregister the user equipment for CS′ and PS, where CS′ means all CSservices except the services not supported (e.g., voice) services on theflexible UTRAN and CS voice on another RAN that may support voice, suchas UMTS or GERAN. MT and/or MO CS (except voice) and PS calls may behandled on flexible UTRAN. When MT CS notification is received at theMSC serving UMTS or GSM, a page may be forwarded to the user equipmentthrough the MSC supporting non-voice CS services or the SGSN (forflexible UTRAN) and user equipment may be redirected to another RAN thatsupports CS voice support, such as GERAN or UTRAN. CN changes may needto be implemented in some cases.

Turning next to FIG. 10, a block diagram illustrates a device 1000 thatincludes mobility functionality in accordance with various embodiments.The device 1000 may be an example of aspects of: the core networks 130of FIG. 1, FIG. 3B, and/or FIG. 11. The device 1000 may also be aprocessor. The device 1000 may include a receiver module 1005, a supportfor circuit-switched services identification module 1010, a core networkredirection module 1015, and/or a transmitter module 1020. Each of thesecomponents may be in communication with each other.

These components of the device 1000 may, individually or collectively,be implemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

The receiver module 1005 may receive information such as packet, data,and/or signaling information regarding what device 1000 has received ortransmitted. The received information may be utilized by the support forcircuit-switched services identification module 1010 and/or core networkredirection module 1015 for a variety of purposes.

In some embodiments, a lack of support for one or more circuit-switchedservices on a flexible bandwidth radio access network of multiple radioaccess networks may be identified by the support for circuit-switchedservices identification module 1010. The circuit-switched (CS) servicefor a user equipment may be redirected at the core network redirectionmodule 1015 from the flexible bandwidth radio access network to a radioaccess network that supports the one or more circuit-switched services.The core redirection module 1015 may modify and/or transmit one or moremessages to intitiate a core network redirection. In some cases, thecircuit-switched service may be a circuit-switched voice service. Theone or more CS services includes at least a CS voice service, a Release99 CS voice service, or a CS voice service over one or more datachannels, for example.

The support for circuit-switched services identification module 1010and/or core network redirection module 1015 may be configured toregister the user equipment with respect to at least one packet switchedservice. Some embodiments of device 1000 may include a registrationmodule to perform this function. Some embodiments include registering,by device 1000 such as through the support for circuit-switched servicesidentification module 1010 and/or core network redirection module 1015,the user equipment over the flexible bandwidth radio access network withrespect to at least one circuit-switched service. The circuit-switchedservice may include a non-voice circuit-switched service, SMS data,and/or CS data. Some embodiments include receiving, at device 1000through the support for circuit-switched services identification module1010 and/or core network redirection module 1015, a registration requestfrom the user equipment on the flexible bandwidth radio access network.

In some cases, the user equipment may be camped on the flexiblebandwidth radio access network. The user equipment may be currently atleast being served by or camped on a flexible bandwidth carrier thatlacks support for a CS service, such as a CS voice service.

In some situations, the device 1000 is aware of the capabilities of theflexible bandwidth radio access network. The flexible bandwidth radioaccess network may be aware that it lacks support for thecircuit-switched service but may not initiate redirection. In someembodiments, the device 1000 may determine that the CS service isunsupported on the flexible bandwidth radio access network and may tuneto another radio access network that supports the CS service. In othersituations, the device 1000 may be unaware that the CS service isunsupported on the flexible bandwidth radio access network.

FIG. 11 shows a block diagram of a communications system 1100 that maybe configured for utilizing mobility for wireless communications systemsin accordance with various embodiments. This system 1100 may includeaspects of the system 100 depicted in FIG. 1, systems 200 of FIG. 2,systems 300 of FIG. 3, and/or system 4200 of FIG. 42; and/or device 1000of FIG. 10. The core network 130-c may include memory 1170, and aprocessor module 1165, which each may be in communication, directly orindirectly, with each other (e.g., over one or more buses). In somecases, the core network 130-c may communicate with other aspects of thenetwork communications module 1175.

Core network 130-c may also communicate with radio access networks121-i/121-j. Radio access networks 121 may be co-located in some cases,or separated located. In some cases, radio access networks 121 mayinclude flexible capable radio access networks and/or normal/legacyradio access networks. Radio access networks 121 may be in wirelesscommunication with user equipment 115-h, which may be flexible capable.In some cases, core network 130-c may communicate with radio accessnetworks 121 utilizing radio access network communication module 1120.

The memory 1170 may include random access memory (RAM) and read-onlymemory (ROM). The memory 1170 may also store computer-readable,computer-executable software code 1171 containing instructions that areconfigured to, when executed, cause the processor module 1165 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 1171 maynot be directly executable by the processor module 1165 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 1165 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 1165 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets, and provide indicationsof whether a user is speaking.

According to the architecture of FIG. 11, the core network 130-c mayfurther include a communications management module 1130. Thecommunications management module 1130 may manage communications otheraspects of communication, such as communication with user equipment115-h. By way of example, the communications management module 1130 maybe a component of the core network 130-c in communication with some orall of the other components of the core network 130-c via a bus.Alternatively, functionality of the communications management module1130 may be implemented as a component of the radio access networkcommunications module 1120, as a computer program product, and/or as oneor more controller elements of the processor module 1165.

The components for core network 130-c may be configured to implementaspects discussed above with respect to device 1000 in FIG. 10 and maynot be repeated here for the sake of brevity. The network identificationmodule 1010-a may be an example of the support for circuit-switchedservices identification module 1010 of FIG. 10. The redirection module1015-a may be an example of the core network redirection module 1015 ofFIG. 10.

The core network 130-c may also include a handover module 1125 that maybe utilized to perform handover procedures of the user equipment 115-hfrom one radio access network 121 to another. For example, the handovermodule 1125 may perform a handover procedure of the user equipment 115-hfrom core network 130-c to another where normal waveforms are utilizedbetween the user equipment 115-h and one of the radio access networks121 and flexible bandwidth waveforms are utilized between the userequipment and another radio access network. The core network 130-c mayalso include a registration module 1115 for registering different userequipment 115 with different services (e.g., CS, PS) through differentRANs 121.

Turning to FIG. 12A, a flow diagram of a method 1200-a for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1200-a may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1100 of FIG. 11, system 4200 of FIG.42; the core networks 130 of FIG. 1, FIG. 3B, and/or FIG. 11 and/ordevice 1000 of FIG. 10.

At block 1205, a lack of support for one or more circuit-switched (CS)services on a flexible bandwidth radio access network may be identifiedat a core network. At block 1210, the one or more CS services for a userequipment may be redirected, at the core network, from the flexiblebandwidth radio access network to a radio access network that supportsthe one or more circuit-switched service from the multiple radio accessnetworks. The one or more circuit-switched services may include acircuit-switched voice service, a Release 99 CS voice service, or a CSvoice service over one or more data channels, for example.

Some embodiment include registering, at the core network, the userequipment over the flexible bandwidth radio access network with respectto at least one packet switched service. Some embodiments includeregistering, at the core network, the user equipment over the flexiblebandwidth radio access network with respect to at least onecircuit-switched service, such as a non-voice CS service, SMS data,and/or CS data. Some embodiments include receiving, at the core network,an attach request from the user equipment over the flexible bandwidthradio access network.

In some cases, the user equipment may be camped on the flexiblebandwidth radio access network. In some cases, the user equipment may becurrently at least being served by or camped on a flexible bandwidthcarrier that lacks support for a circuit-switched service, such as a CSvoice service.

In some situations, the core network is aware of the capabilities of theflexible bandwidth radio access network. The flexible bandwidth radioaccess network may be aware that it lacks support for thecircuit-switched service but may not initiate redirection. In othercases, the core network may determine that the CS service, such as CSvoice service, is unsupported on the flexible bandwidth radio accessnetwork. In some cases, the core network may be unaware that thecircuit-switched service, such as CS voice service, is unsupported onthe flexible bandwidth radio access network.

Turning to FIG. 12B, a flow diagram of a method 1200-b for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1200-b may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1100 of FIG. 11, system 4200 of FIG.42; the core networks 130 of FIG. 1, FIG. 3B, and/or FIG. 11 and/ordevice 1000 of FIG. 10. Method 1200-b may be an example of one or moreaspects of method 1200-a of FIG. 12A.

A core network may register a user equipment (UE) through at least oneradio access network from multiple radio access networks at block 1215.Identifying, at the core network, a lack of support for a certaincircuit-switched service, such as a voice service, on a flexiblebandwidth radio access network of the multiple of radio access networksmay occur at block 1205-a. Registering, at the core network, thecircuit-switched voice service for the UE through a radio access networkthat supports the circuit-switched voice service from the multiple radioaccess networks may occur at block 1220.

Turning to FIG. 12C, a flow diagram of a method 1200-c for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1200-b may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1100 of FIG. 11, system 4200 of FIG.42; the core networks 130 of FIG. 1, FIG. 3B, and/or FIG. 11 and/ordevice 1000 of FIG. 10. Method 1200-c may be an example of one or moreaspects of method 1200-a of FIG. 12A and/or method 1200-b of FIG. 12B.

At block 1225, a registration request for the UE may be received at acore network through a flexible bandwidth radio access network. Theregistration request may be with respect to both a CS and PS domain, forexample. In some cases, the registration request may be with respect toa CS voice service, a PS service, and/or a non-voice CS service. Atblock 1230, the core network may register the user equipment with theflexible bandwidth radio access network with respect to at least one ofthe PS service or the non-voice CS service. At block 1205-b, the corenetwork may identify a lack of support for a CS voice service on theflexible bandwidth radio access network of the multiple of radio accessnetworks. At block 1220-a, the core network may register the CSvoiceservice for the UE through a radio access network that supports thecircuit-switched voice service from the multiple radio access networks.At block 1210-a, the core network may redirect the CS voice service fora user equipment from the flexible bandwidth radio access network to theradio access network that supports the circuit-switched service from themultiple radio access networks.

Methods, systems, and devices for providing mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. These methods, systems, and devices maybe implemented utilizing device 1300 of FIG. 13, system 1400 of FIG. 14,method 1500-a of FIG. 15A, method 1500-b of FIG. 15B, and/or method 1600of FIG. 16, for example. Some examples provide for radio access network(RAN) determining support for circuit-switched (CS) services, such as CSvoice services, and in the case of lack of support for such servicesover a flexible bandwidth system, redirecting the user equipment forsuch services to a radio access network that supports such services.Embodiments may include: communicating with a user equipment over aflexible bandwidth radio access network from multiple radio accessnetworks; and determining, by the flexible bandwidth radio accessnetwork, to redirect a circuit-switched service for the user equipmentto a radio access network that supports the circuit-switched servicefrom the multiple radio access networks.

The flexible bandwidth radio access network may redirect thecircuit-switched service for the user equipment to the radio accessnetwork that supports the circuit-switched service from the multipleradio access networks. In many cases, the flexible bandwidth radioaccess network and the radio access network that supports the additionalservices (e.g., circuit switched services) may be part of the sameequipment. For example, a single nodeB may include multiple cells. As anexample, one cell may support the flexible bandwidth radio accessnetwork and another may support the radio access network that supportsthe additional services. In some cases, the flexible radio accessnetwork may transmit one or more messages to a core network such thatthe core network redirects the circuit switched service for the userequipment to the radio access network that supports the circuit-switchedservice from the multiple radio access networks. Other services (e.g.,PS services and non-voice CS services) may be handled by the flexiblebandwidth radio access network. Some examples include handling apacket-switched service on the flexible bandwidth radio access network.A non-voice circuit-switched service may be handled on the flexiblebandwidth radio access network in some cases. In other cases, theflexible bandwidth radio access network may support voice services insome cases.

The core network (CN) may not be aware that the flexible bandwidth RANmay not support some CS services, like CS voice services. The corenetwork may be unaware of a flexible bandwidth capability of the radioaccess network (i.e., does not distinguish a flexible bandwidth radioaccess network from a normal bandwidth radio access network in terms oftypes of services supported). In other cases, the core network may beaware that the flexible bandwidth RAN may not support some CS services,like CS voice services. However, the CN may not handle redirection of CSvoice services but rather may let the flexible bandwidth radio accessnetwork handle the redirection. In other cases, the core network may beaware that the flexible bandwidth RAN may not support some CS services.However, the CN (or another knowledgeable entity) may handle some butnot all of the redirections of the CS services allowing the RAN tohandle and/or initiate the redirection.

In some examples, Location Area (LA) and/or Routing Area (RA) forflexible bandwidth UMTS, UMTS, and GSM may be overlapping but notnecessarily the same as the cell sizes are different. The flexiblebandwidth UMTS and UMTS and/or GSM cells may overlap partially orcompletely. The SGSN and MSC serving UMTS, GSM and flexible bandwidthUMTS networks may be the same. This may be the case, for example, whenUMTS, GSM, and flexible bandwidth UMTS are deployed at the same site. Insome examples, flexible bandwidth UTRAN supports CS SMS and other CSservices except CS voice call. For CS voice, it may support some CSvoice related signaling (e.g., Paging Type 2 message for MT CS voicecall when user equipment is in PS call).

Some examples include a situation where a user equipment may be campingon a flexible bandwidth UTRAN. The user equipment may perform a combinedIMSI and GPRS Attach with the CN through the flexible bandwidth UTRAN.In some examples, the CN is not aware that flexible bandwidth UTRAN doesnot support voice services, so it may register the user equipment for CSand PS services over the flexible bandwidth UTRAN. For example, MT/MO CS(except voice) and PS calls may be handled on flexible bandwidth UTRAN.For example, when setting up a mobile terminated (MT) CS voice call, RANredirection may be utilized to direct the CS voice call in a radioaccess network that supports CS voice call. The procedure may beimplemented as such as: when a MT CS notification is received at theMSC, a page may be sent to the user equipment and user equipment may beredirected to a radio access network that supports CS voice, such as GSMor UMTS by the flexible bandwidth UTRAN. Similarly, when setting up a MOCS voice call, the flexible bandwidth UTRAN may redirect the call to aradio access network that supports CS voice, such as GSM or UMTS.

Some examples may handle situations where there is no CS support on theflexible bandwidth RAN, such as a flexible bandwidth UTRAN and the CN isaware that flexible bandwidth UTRAN does not offer CS services but theCN does not handle redirection and acts the same way as if flexiblebandwidth UTRAN supports all CS services. Mobiles may do combined IMSIand GPRS Attach, for example. For MO/MT CS voice call, redirection by aflexible bandwidth UTRAN to a radio access network that supports CSvoice, such as GSM or UMTS, may be used.

Some examples may handle situations where there may be support for CSservices except voice on a flexible bandwidth RAN, such as a flexiblebandwidth UTRAN. For example, a flexible bandwidth UTRAN may support CSsignaling (e.g., Paging Type 2 message for MT CS voice call when userequipment is in PS call) and might or might not support SMS and CS dataservices but does not support CS voice call. The CN may not be aware ofthis lack of voice support. Redirection by flexible bandwidth UTRAN maybe utilized. In some cases, the CN may ensure that the user equipment isregistered with the appropriate MSC and SGSN using a combined IMSI andGPRS Attach. The MSC and the SGSN might support different RATs.

The following describes some embodiments where there may be no CSsupport on a flexible bandwidth RAN, such as a flexible bandwidth UTRAN.Merely by way of example, a user equipment may be camping on theflexible bandwidth UTRAN and perform combined GPRS and IMSI Attach (onthe CS and PS domain) with the CN through the flexible bandwidth UTRAN.In some cases, the GPRS Attach is received by the SGSN and the userequipment is registered on the PS domain at the SGSN. The IMSI attachrequest maybe received by the SGSN and forwarded to the appropriate MSC.Though the CN may be aware of the lack of support for some CS servicesover flexible bandwidth RAN, the redirection may be handled by the RAN.

Some embodiments include a flexible bandwidth system where CS signalingmay be supported by a flexible bandwidth RAN, but there may be no voicesupport on the flexible bandwidth RAN, such as a flexible bandwidthUTRAN. For example, a user equipment may be camping on the flexiblebandwidth UTRAN. RAN redirection may be utilized to move the UE to RANthat supports CS voice. The user equipment may perform a combined IMSIand GPRS Attach with the CN through the flexible UTRAN. The UEregistration may be for a combined CS′ (where CS′ means all CS servicesexcept certain CS services such as CS voice) and PS registration. As aresult, the CN may be made aware that some CS signaling and maybe someservices (e.g., SMS, CS Data etc.) are supported on flexible UTRAN, butnot voice. Therefore, CS voice services for that UE may be supported byanother RAN such as UMTS or GSM and MT/MO CS (except voice) and PS callsmay be handled on flexible UTRAN.

Turning next to FIG. 13, a block diagram illustrates a device 1300 thatincludes mobility functionality in accordance with various embodiments.The device 1300 may be an example of aspects of the core networks 130 ofFIG. 1, FIG. 3B, and/or FIG. 14. The device 2100 may also be aprocessor. The device 1300 may include a receiver module 1305, aredirection determination module 1310, a RAN redirection module 1315,and/or a transmitter module 1320. Each of these components may be incommunication with each other. Furthermore, the redirectiondetermination module 1310 may also communicate with the other networkentities (e.g., MSC, SGSN, CN). Both the redirection determinationmodule 1310 and/or the RAN redirection module 1315 may determine itsactions based on messages and signalling directed to other entitieswithin the RAN and outside the redirection determination module 1310and/or the RAN redirection module 1315. Furthermore, the redirectiondetermination module 1310 and/or the RAN redirection module 1315 maymodify messages and signaling directed to other modules. Modifying mayinclude remove a message or fields in a message. These messages may bedirected or directed to entities outside the redirection determinationmodule 1310 and/or the RAN redirection module 1315 (e.g., UE, RAN, CN).Furthermore, the redirection determination module 1310 and/or the RANredirection module 1315 can generate new messages and signaling orremove messages and signaling directed to other modules

These components of the device 1300 may, individually or collectively,be implemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

The receiver module 1305 may receive information such as packet, data,and/or signaling information regarding what device 1300 has received ortransmitted. The received information may be utilized by the redirectiondetermination module 1310 and/or the RAN redirection module 1315 for avariety of purposes.

In some embodiments, device 1300 through transmitter module 1320 and/orreceiver module 1305 may be configured for communicating with a userequipment using a flexible bandwidth radio access network from multipleradio access networks. The redirection determination module 1310 and/orthe RAN redirection module 1315 may be configured for determining toredirect a circuit-switched service for the user equipment to a radioaccess network that supports the circuit-switched service from themultiple radio access networks.

The redirection determination module 1310 and/or the RAN redirectionmodule 1315 may be configured such that redirecting the circuit-switchedservice may occur at the flexible bandwidth radio access network.Redirecting the circuit-switched service may occur at a core network.Some embodiments include transmitting one or more message from device1300 through the redirection determination module 1310, the RANredirection module 1315, and/or the transmitter module 1320 to the corenetwork to prompt the redirection. The redirection determination module1310 and/or the RAN redirection module 1315 may be configured forredirecting, at the flexible bandwidth radio access network, thecircuit-switched service for the user equipment to the radio accessnetwork that supports the circuit-switched service from the plurality ofradio access networks. The redirection determination module 1310 and/orthe RAN redirection module 1315 may be configured for transmitting oneor more messages to a core network such that the core network redirectsthe circuit switched service for the user equipment to the radio accessnetwork that supports the circuit-switched service from the plurality ofradio access networks. The redirection determination module 1310 and/orthe RAN redirection module 1315 may modify one or more messages to acore network such that the core network redirects the circuit switchedservice for the user equipment to the radio access network that supportsthe circuit-switched service from the multiple radio access networks.

Some embodiments of device 1300 being configured to handle apacket-switched service on the flexible bandwidth radio access network.Some embodiments include handling another circuit-switched service onthe flexible bandwidth radio access network. The other circuit-switchedservice may include a non-voice circuit-switched service or acircuit-switched voice service.

In some situations, the core network is unaware that thecircuit-switched voice service is unsupported on the flexible bandwidthradio access network. In some cases, the core network may be unaware ofa flexible bandwidth capability of the flexible bandwidth radio accessnetwork. In some cases, the core network may be aware of a flexiblebandwidth capability of the flexible bandwidth radio access network. Insome cases, the core network is unaware of a flexible bandwidthcapability of the flexible bandwidth radio access network.

FIG. 14 shows a block diagram of a communications system 1400 that maybe configured for mobility for wireless communications systems inaccordance with various embodiments. This system 1400 may includeaspects of the system 100 depicted in FIG. 1, systems 200 of FIG. 2,systems 300 of FIG. 3, and/or system 4200 of FIG. 42; and/or device 1300of FIG. 13. The radio access network 121-d may include aspects of a basestation 105 and/or a controller 120 to represent a combined systemand/or separate components that may comprise part of a radio accessnetwork. The radio access network 121-d may include antennas 1445, atransceiver module 1450, memory 1470, and a processor module 1465, whicheach may be in communication, directly or indirectly, with each other(e.g., over one or more buses). The transceiver module 1450 may beconfigured to communicate bi-directionally, via the antennas 1445, withthe user equipment 115-i, which may be a multi-mode user equipment. Thetransceiver module 1450 (and/or other components of the radio accessnetwork 121-d) may also be configured to communicate bi-directionallywith one or more networks. In some cases, the radio access network 121-dmay communicate with the network 130-d through network communicationsmodule 1475. Radio access network 121-d may be an example of an eNodeBbase station, a Home eNodeB base station, a NodeB base station, a RadioNetwork Controller (RNC), and/or a Home NodeB base station.

Radio access network 121-d may also communicate with other base stations105, such as base station 105-m and base station 105-n. Each of the basestations 105 may communicate with user equipment 115-i using differentwireless communications technologies, such as different Radio AccessTechnologies. In some cases, radio access network 121-d may communicatewith other base stations such as 105-m and/or 105-n utilizing basestation communication module 1431. In some embodiments, base stationcommunication module 1431 may provide an X2 interface within an LTEwireless communication technology to provide communication between someof the base stations 105. In some embodiments, radio access network121-d may communicate with other base stations through controller 120-aand/or network 130-d.

The memory 1470 may include random access memory (RAM) and read-onlymemory (ROM). The memory 1470 may also store computer-readable,computer-executable software code 1471 containing instructions that areconfigured to, when executed, cause the processor module 1465 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 1471 maynot be directly executable by the processor module 1465 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 1465 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 1465 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets, and/or provideindications of whether a user is speaking.

The transceiver module 1450 may include a modem configured to modulatethe packets and provide the modulated packets to the antennas 1445 fortransmission, and to demodulate packets received from the antennas 1445.While some examples of the radio access network 121-d may include asingle antenna 1445, the radio access network 121-d preferably includesmultiple antennas 1445 for multiple links which may support carrieraggregation. For example, one or more links may be used to support macrocommunications with user equipment 115-i.

According to the architecture of FIG. 14, the radio access network 121-dmay further include a communications management module 1430. Thecommunications management module 1430 may manage communications withother base stations 105 or RNC 120. By way of example, thecommunications management module 1430 may be a component of the radioaccess network 121-d in communication with some or all of the othercomponents of the radio access network 121-d via a bus. Alternatively,functionality of the communications management module 1430 may beimplemented as a component of the transceiver module 1450, as a computerprogram product, and/or as one or more controller elements of theprocessor module 1465.

The components for radio access network 121-d may be configured toimplement aspects discussed above with respect to device 1300 of FIG. 13and may not be repeated here for the sake of brevity. The redirectionmodule 1315-a may be an example of the RAN redirection module 1315-a.The redirection determination module 1310-a may be an example of theredirection determination module 1310-a.

The radio access network 121-d may also include a spectrumidentification module 1415. The spectrum identification module 1415 maybe utilized to identify spectrum available for flexible bandwidthwaveforms. Some embodiments may include a circuit-switched supportidentification module 1420 to determine if other aspects of system 1400include support for circuit-switched services, such as CS voiceservices. In some embodiments, a handover module 1425 may be utilized toperform handover procedures of the user equipment 115-i from one basestation 105 to another. For example, the handover module 1425 mayperform a handover procedure of the user equipment 115-i from radioaccess network 121-d to another where normal waveforms are utilizedbetween the user equipment 115-i and one of the base stations andflexible bandwidth waveforms are utilized between the user equipment andanother base station. A scaling module 1427 may be utilized to scaleand/or alter chip rates to generate flexible bandwidth waveforms.

In some embodiments, the transceiver module 1450 in conjunction withantennas 1445, along with other possible components of radio accessnetwork 121-d, may transmit and/or receive information regardingflexible bandwidth waveforms and/or scaling factors from the radioaccess network 121-d to the user equipment 115-i, to other base stations105-m/105-n, or core network 130-d. In some embodiments, the transceivermodule 1450 in conjunction with antennas 1445, along with other possiblecomponents of radio access network 121-d, may transmit and/or receiveinformation to or from the user equipment 115-i, to or from other basestations 105-m/105-n, or core network 130-d, such as flexible bandwidthwaveforms and/or scaling factors, such that these devices or systems mayutilize flexible bandwidth waveforms.

Turning to FIG. 15A, a flow diagram of a method 1500-a for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1500-a may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1400 of FIG. 14, system 4200 of FIG.42; the radio access networks 121 of FIG. 14; and/or device 1300 of FIG.13.

Communicating with a user equipment over a flexible bandwidth radioaccess network may occur at block 1505, where the flexible bandwidthradio access network is from a group of radio access networks.Determining, by the flexible bandwidth radio access network, to redirecta circuit-switched service for the user equipment to a radio accessnetwork that supports the circuit-switched service from the multipleradio access networks may occur at block 1510.

For method 1500-a, redirecting the circuit-switched service may occur atthe flexible bandwidth radio access network. Redirecting thecircuit-switched service may occur at a core network. Some embodimentsinclude transmitting one or more message from the flexible bandwidthradio access network to the core network to initiate and/or facilitatethe redirection. Method 1500-a may include redirecting, at the flexiblebandwidth radio access network, the circuit-switched service for theuser equipment to the radio access network that supports thecircuit-switched service from the multiple radio access networks. Method1500-a may include transmitting one or more messages to a core networksuch that the core network redirects the circuit switched service forthe user equipment to the radio access network that supports thecircuit-switched service from the multiple radio access networks. Someembodiments include modifying one or more messages to a core networksuch that the core network redirects the circuit switched service forthe user equipment to the radio access network that supports thecircuit-switched service from the plurality of radio access networks.

Some embodiments include handling a packet-switched service on theflexible bandwidth radio access network. Some embodiments includehandling another circuit-switched service on the flexible bandwidthradio access network. The other circuit-switched service may include anon-voice circuit switched service or a circuit-switched voice service.

In some situations, the core network may be unaware of a flexiblebandwidth capability of the flexible bandwidth radio access network. Forexample, the core network may be unaware that the circuit-switched voiceservice is unsupported on the flexible bandwidth radio access network.In other situations, the core network may be aware of a flexiblebandwidth capability of the flexible bandwidth radio access network. Insome situations, the core network is aware that the circuit-switchedservice is unsupported on the flexible bandwidth radio access network.

Turning to FIG. 15B, a flow diagram of a method 1500-b for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1500-b may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1400 of FIG. 14, system 4200 of FIG.42; the radio access networks 121 of FIG. 14; and/or device 1300 of FIG.13. Method 1500-b be may be an example of one or more aspects of method1500-a of FIG. 15A.

At block 1505-a, communicating with a user equipment over a flexiblebandwidth radio access network, where the flexible bandwidth radioaccess network is from a group of multiple radio access networks mayoccur. At block 1515, at least a packet-switched service or a non-voicecircuit-switched service may be handled on the flexible bandwidth radioaccess network. At block 1510-a, the flexible bandwidth radio accessnetwork may determine to redirect at a core network a circuit-switchedservice for the user equipment to a radio access network that supportsthe circuit-switched service from the multiple radio access networks. Atblock 1520, one or more messages may be transmitted from the flexiblebandwidth radio access network to the core network to initiate theredirection.

Turning to FIG. 15C, a flow diagram of a method 1500-c for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1500-c may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1400 of FIG. 14, system 4200 of FIG.42; the radio access networks 121 of FIG. 14; and/or device 1300 of FIG.13. Method 1500-c be may be an example of one or more aspects of method1500-a of FIG. 15A and/or method 1500-b of FIG. 15B

At block 1505-b, communicating with a user equipment over a flexiblebandwidth radio access network may occur. The flexible bandwidth radioaccess network may be from a group of multiple radio access networks. Atblock 1510-b, the flexible bandwidth radio access network may determineto redirect a circuit-switched voice service for the user equipment to aradio access network that supports the circuit-switched voice servicefrom the multiple radio access networks. At block 1525, the flexiblebandwidth radio access network may redirect the circuit-switched voiceservice for the user equipment to the radio access network that supportsthe circuit-switched service from the plurality of radio accessnetworks.

Turning to FIG. 16, a flow diagram of a method 1600 for providingmobility within wireless communications systems is provided inaccordance with various embodiments. Method 1600 may be implementedutilizing various wireless communications devices and/or systemsincluding, but not limited to: system 100 of FIG. 1, systems 200 of FIG.2, systems 300 of FIG. 3, system 1100 of FIG. 11, system 1400 of FIG.14, system 4200 of FIG. 42; the core network 130 of FIG. 11; the radioaccess networks 121 of FIG. 14; and/or device 1300 of FIG. 13. Method1600 be may be an example of one or more aspects of method 1500-a ofFIG. 15A, method 1500-b of FIG. 15B, method 1200-a of FIG. 12A, and/ormethod 1200-b of FIG. 12B.

At block 1605, a user equipment may be registered for a packet-switchedservice on a first radio access network that includes a flexiblebandwidth network. At block 1610, it may be determine that acircuit-switched service, such as a voice service, is unsupported on thefirst radio access network. At block 1615, the UE may be registered forthe circuit-switched service on a second radio access network thatsupports the circuit-switched service, which may include a normalbandwidth access network.

Methods, systems, and devices facilitating mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. The methods, systems, and/or devices maybe implemented utilizing one or more aspects of system 2500 of FIG. 25,the system 2600 of FIG. 26, user equipment 2700 of FIG. 27, method2800-a of FIG. 28A, and/or method 2800-b of FIG. 28B, for example. Someembodiments provide for transitioning or spring forward to a flexiblebandwidth system. Spring forward may include the transition from anormal bandwidth carrier (e.g., GSM, UMTS) to a flexible bandwidthcarrier. Some embodiment may include transitioning from a first radioaccess network to a second radio access network, where the first radioaccess network includes a normal bandwidth radio access network and thesecond radio access network includes a flexible bandwidth radio accessnetwork. Some embodiments include a method for facilitating mobility toa flexible bandwidth system that may include: communicating over firstradio access network, where the first radio access network utilizes afirst bandwidth carrier; identifying a second radio access network,where the second radio access network utilizes a first flexiblebandwidth carrier; and transitioning from utilizing the first bandwidthcarrier of the first radio access network to utilizing the firstflexible bandwidth carrier of the second radio access network. The firstbandwidth carrier may be a normal bandwidth carrier or a second flexiblebandwidth carrier different from the first flexible bandwidth carrier.

A core network may direct one or more aspects of the transitioning. Atleast one of the radio access networks directs one or more aspects ofthe transitioning in some embodiments. The transitioning may relate topacket-switched services for a user equipment. The transitioning mayutilize a variety of different procedures including, but not limited to,a load-based handover procedure, a service-based handover procedure,and/or a inter-frequency handover procedure. When the handover involvesone service, it may be called a single Radio Access Bearer (RAB)handover and when multiple services (e.g., CS and PS call) may beinvolved, the handover may be referred to as a multi-RAB handover. Thesehandover procedures may also involve the user equipment takingmeasurements from the new cell or the handover could be performedblindly.

Some embodiments include a load-based handover for transitioning to aflexible bandwidth system. Some embodiments include a load-basedhandover for transitioning to a flexible bandwidth system. Load-basedhandover are used typically triggered in networks when a particularnetwork can not support adding a new call on its network so it handoversthe associated UE to another network. For handover, between normalbandwidth and flexible bandwidth system, load-based handover procedurecan be used triggered when services could be better supported on theflexible bandwidth network. The reason for triggering the load-basedhandover in the scenario is not necessarily due to the load on thenormal bandwidth network. For example, a load-based handover may beutilized to transition or spring forward from GSM to a flexible system.For example, while entering the GSM network, a UE may perform a combinedGPRS and IMSI Attach on the GSM network after which the UE camps on thecell. The UE may initiate a MO PS call or may receive a MT PS call (withdata rate that can be supported on the flexible bandwidth network butnot on GERAN, for example). The user equipment may send a servicerequest and may set-up a PDP context for the call. GSM network mayaccept the calls and may assign appropriate bearer resources to supportthe PS call and may establish a PS connection with the user equipment.GERAN may decide that the QoS can be served by flexible bandwidth UMTScell so RAN may initiate relocation to a flexible bandwidth UTRAN targetcell. The flexible bandwidth UMTS target cell may be determined from adatabase at the RAN containing a list of geographically overlapping orneighboring UMTS and flexible bandwidth UMTS cells, for example. GERANmay request that the user equipment perform inter-RAT measurements onthe target flexible bandwidth UMTS cell before issuing a Cell ChangeOrder command to user equipment. In some embodiments, this may be doneif user equipment may not be known to support flexible bandwidth UTRAN.If user equipment detects flexible bandwidth UMTS target cell and mayreport suitable signal strength to GERAN, GERAN may send a “Cell Changeorder to UTRAN” command to the user equipment. In case measurements arenot configured for the user equipment, GERAN may blindly send a CellChange Order command to the user equipment to tune to the targetflexible bandwidth UMTS cell. This may be done if user equipment isknown to support flexible bandwidth UTRAN, for example. In someembodiments, measurements are configured so that the user equipment mayidentify the target flexible bandwidth UMTS cell before being handedover, which may avoid call drops especially for non-flexible and/ornormal user equipment, which may not be able to detect flexiblebandwidth UMTS cell. This embodiment includes situations where there maybe no ongoing CS voice call. Also, it may be possible that if requesteddata rate can be supported by GERAN, the PS call is not handed over toflexible bandwidth UTRAN.

A service-based handover for transitioning to a flexible bandwidthsystem may be utilized in some cases. For example, a service-basedhandover (SBHO) may be utilized to transition or spring forward from GSMto a flexible bandwidth UMTS. For example, a redirect of a flexiblebandwidth capable UE from GSM to flexible bandwidth UTRAN may occur whena PS call is attempted by the UE. Service-based HO procedure may beutilized and the UE maybe notified of the handover with the Cell ChangeOrder message. The Cell Change Order (CCO) message sent from the GERANto the UE regarding the flexible bandwidth UTRAN cell may be sent afterthe UE takes measurement on the flexible bandwidth UTRAN cell or blindlyby the GERAN. The GERAN might or might not know if UE is flexiblebandwidth capable before ordering the measurements or sending the CCO.In some cases, the GERAN may be able to obtain additional information todetermine if the UE has flexible capabilities. For supporting PSservices on the flexible bandwidth networks, the SGSN, if aware of theUE capability, may selectively perform SBHO for flexible bandwidthcapable UEs based on UEIDs such as IMEI. Note that in some embodiments,SBHO may include the SGSN notifying the BSC to perform a HO to flexiblebandwidth UTRAN.

Some embodiments may utilize handover procedures based on nomeasurements and/or based on user equipment measurements. Forload-based, service-based, and/or inter-frequency handovers, forexample, before the network communicates the handover to the UE, itcould ask the UE to take measurements or not of the target cell. Forexample, some embodiments include mobile-assisted (UE measurement-based)handover where, for example, compressed mode gaps (measurement gaps) maybe scheduled for inter-frequency measurements to find suitable targetcell. This may be utilized when a user equipment may not be known tosupport flexible bandwidth. Some embodiments utilize database and/ornetwork assisted handover, for example, which may include nomeasurements performed on other frequencies; rather cell mappinginformation may be stored in data base is used to identify the targetcell. This approach may be done when user equipment may already be knownto support flexible bandwidth. For example, cell mapping information maybe available at RAN from the knowledge of collocated flexible andGSM/UMTS cells. User equipment capability information may be built upover time by RAN—from previous user equipment measurements reported toRAN, for example. Subsequently, when a user equipment may be known to beflexible bandwidth compatible, blind HO may be done.

An inter-frequency handover (IFHO) from a normal bandwidth system to aflexible bandwidth system may be utilized in some cases. Someembodiments may be non-measurement based. For example, a user equipmentmay camp on the UMTS network and may receive a MT PS call (with bit ratethat can be supported on the flexible bandwidth network) or may decideto establish an MO PS call. The user equipment may send a servicerequest and may set-up a PDP context for the call. UMTS network mayaccept the calls and may assign appropriate RAB resources to support thePS call and may establish a PS connection with the user equipment. Usinga RAN preference algorithm, the RAN may decide that the QoS can beserved by flexible bandwidth UMTS cell so RAN may initiate an relocationto a flexible bandwidth UMTS target cell. The flexible bandwidth UMTStarget cell may be determined from a database at the RAN containing alist of geographically overlapping or neighboring UMTS and flexiblebandwidth UMTS cells. In some embodiments, the RAN can request that theuser equipment perform inter-frequency measurements on the target cellbefore issuing a handover to user equipment. If user equipment finds thetarget cell and reports favorable signal strength to the UMTS RAN, then,the UMTS RAN may send a “physical channel reconfiguration” message tothe user equipment. In case measurements are not issued, the UMTS mayblindly send a “physical channel reconfiguration” message to the userequipment to tune to the target. In some embodiments, the user equipmentidentifies the target cell before being handed over to avoid call dropsespecially for non-flexible or normal UMTS user equipment.

Some embodiments may include an inter-frequency handover that may besimilar to the load-based handover with some differences. For example,one difference may be that the inter-frequency HO may be triggered basedon the measured signal strength of the user equipment. Once the measuredsignal strength may be past a threshold, the user equipment may signalthe event to the UMTS RAN (UTRAN) and the relocation required commandmay be issued by the RAN to the SGSN. The HO procedure may then proceedsimilar to the load-based handover. The difference between the IFHO andthe load-based handover may be that only the user equipment (flexiblebandwidth UMTS user equipment, for example) that may identify theflexible bandwidth UMTS's cell may be triggered to be handed over to thetarget cell. Some embodiments may include multi-RAB scenarios. Forexample, in case of an existing PS call on the UMTS RAN, if another MTor MO PS call may be received by the network, another RAB might beset-up for such call. Similar to the single RAB scenario, if flexiblebandwidth UMTS cell supports the multiple RAB services, a load-basedhandover or an inter-frequency handover may be for transitioning the UEfrom a normal bandwidth cell to a flexible bandwidth cell.

Some embodiments involve a preferred radio access technology (RAT) thatthe user equipment may camp on. For example, for voice centric userequipment, GSM may be a preferred RAT. For low and/or medium data ratecentric user equipment, flexible bandwidth UMTS may be a preferred RATor a preferred mode of a RAT. For high data rate centric user equipment,UMTS/HSPA may be a preferred RAT or a preferred mode of a RAT.

Turning next to FIG. 17, a block diagram illustrates a device 1700 thatincludes mobility functionality in accordance with various embodiments.The device 1700 may be an example of aspects of: the core networks 130of FIG. 1, FIG. 3B, FIG. 25, and/or FIG. 26; the radio access networks121 of FIG. 3B, FIG. 25, and/or FIG. 26; and/or the user equipment 115of FIG. 1, FIG. 2, FIG. 3, FIG. 25, FIG. 26, and/or FIG. 27. The device2100 may also be a processor. The device 1700 may include a receivermodule 1705, a network identification module 1710, a spring forwardmodule 1715, and/or a transmitter module 1720. Each of these componentsmay be in communication with each other. Device 1700 may be configuredto implement different aspects of the call flows and/or systems as shownin FIGS. 4-20 and/or associated description.

These components of the device 1700 may, individually or collectively,be implemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

The receiver module 1705 may receive information such as packet, data,and/or signaling information regarding what device 1700 has received ortransmitted. The received information may be utilized by the networkidentification module 1710 and/or spring forward module 1715 for avariety of purposes.

In some embodiments, spring forward module 1715 is configured fortransitioning from a first radio access network to a second radio accessnetwork, wherein the first radio access network includes a normalbandwidth radio access network and the second radio access networkincludes a flexible bandwidth radio access network may occur. In someembodiments, a core network directs one or more aspects of thetransitioning through spring forward module 1715. At least one of theradio access networks directs one or more aspects of the transitioningthrough spring forward module 1715 in some embodiments. Thetransitioning may relate to packet-switched services for a UE. Thespring forward module 1715 may utilize a variety of different proceduresincluding, but not limited to, a load-based handover procedure, aservice-based handover procedure, an inter-frequency handover procedure,and/or a multi-RAB load-based procedure, a multi-RAB service-basedprocedure and/or multi-RAB inter-frequency handover procedure. Thesehandovers may involve the user equipment taking measurements from thenew cell or the handover could be performed blindly.

The receiver module 1705 and/or the transmitter module 1720 may beconfigured to communicate over first radio access network, wherein thefirst radio access network utilizes a first bandwidth carrier. Thenetwork identification module 1710 may be configured for identifying asecond radio access network, wherein the second radio access networkutilizes a first flexible bandwidth carrier. The spring forward module1715 may be configured for transitioning from utilizing the firstbandwidth carrier of the first radio access network to utilizing thefirst flexible bandwidth carrier of the second radio access network.After transitioning to the first flexible bandwidth carrier, thereceiver module 1705 and/or the transmitter module 1720 may beconfigured to communicate over second radio access network, wherein thesecond radio access network utilizes a first flexible bandwidth carrier.

Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may be directed at least in part by acore network. Transitioning from utilizing the first bandwidth carrierof the first radio access network to utilizing the first flexiblebandwidth carrier of the second radio access network may be directed atleast in part by at least one of the radio access networks. In someembodiments, the network identification module 1710 may be configuredfor performing one or more of these transitioning steps. The firstbandwidth carrier may include a normal bandwidth carrier or a secondflexible bandwidth carrier different from the first flexible bandwidthcarrier.

Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may relate to packet-switchedservices for a user equipment. Transitioning from utilizing the firstbandwidth carrier of the first radio access network to utilizing thefirst flexible bandwidth carrier of the second radio access network mayinclude utilizing a load-based handover. Transitioning from utilizingthe first bandwidth carrier of the first radio access network toutilizing the first flexible bandwidth carrier of the second radioaccess network may include utilizing a service-based handover.Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may include utilizing a blindhandover. Transitioning from utilizing the first bandwidth carrier ofthe first radio access network to utilizing the first flexible bandwidthcarrier of the second radio access network may include utilizing userequipment measurements. For example, a single RAB load-based handoverprocedure, a single RAB service-based handover procedure, a single RABinter-frequency handover procedure, a multi-RAB load-based, a multi-RABservice-based, and/or multi-RAB inter-frequency handover procedure mayinvolve the user equipment taking measurements from the new cell or thehandover could be performed blindly. Transitioning from utilizing thefirst bandwidth carrier of the first radio access network to utilizingthe first flexible bandwidth carrier of the second radio access networkmay include utilizing an inter-frequency handover. Transitioning fromutilizing the first bandwidth carrier of the first radio access networkto utilizing the first flexible bandwidth carrier of the second radioaccess network may include utilizing a multi-RAB inter-frequency,service-based, and/or load-based handover.

In some embodiments, the network identification module 1710 may beconfigured for performing one or more of these transitioning steps. Insome embodiments, the network identification module 1710 may beconfigured for determining a preferred radio access technology for auser equipment to camp on based on whether the user equipment is voicecentric or data centric.

Some embodiments of device 1700 may provide mobility from a normaland/or non-flexible bandwidth systems to flexible bandwidth systems. Thenormal and/or non-flexible bandwidth systems may be configured to handlecircuit-switched voice services. The mobility between flexible bandwidthsystems and non-flexible or normal bandwidth systems and/orcircuit-switched voice-supporting systems may be referred to astransitioning between these systems and/or spring forward. For example,some embodiments may include transition from a normal and/ornon-flexible RAN to a flexible RAN. In some embodiments, a flexible RANor flexible bandwidth capable UE may also be capable of normal RAN ornormal UE functionality. Thus, a flexible RAN or flexible bandwidthcapable UE may be a flexible-capable and normal-capable RAN or UE,respective.

The transitioning or spring forward procedures may utilize a variety oftechniques in accordance with various embodiments. Different embodimentsmay utilize different techniques for these transitioning and/or springforward procedures including, but not limited to, single RABload-basedhandover, single RAB service-based handover, single RAB inter-frequencyhandover, multi-RAB inter-frequency, multi-RAB service-based, and/ormulti-RAB load-based handover. Some embodiments include specificregistration procedures. Some embodiments include idle mode campingstrategies. Merely by way of example, some embodiments includetransitioning and/or spring forward from GSM to flexible bandwidth UMTS.In other example, transitioning and/or spring forward may be from UMTSto flexible bandwidth UMTS. Other embodiments may utilize other RATs.

Merely by way of example, some embodiments include registration whilecamping on a specific RAT, such as GSM or UMTS. A UE may performcombined GPRS/IMSI Attach, for example. IMSI Attach may be received bythe MSC and the UE may be registered on the CS domain at the MSCsupporting the GSM or UMTS RAT, for example. GPRS Attach may beforwarded to SGSN of the GSM or UMTS network with overlapping routingareas with the flexible bandwidth UMTS routing areas.

In some embodiments, a UE may idle on a normal RAT or a flexiblebandwidth RAT. For example, a voice centric UEs could use GSM as apreferred RAT. Low/medium data rate centric UEs could use a flexiblebandwidth UMTS as a preferred RAT. A high data rate centric UE could useUMTS or HSPA as preferred RAT. These are merely examples, and othernormal and/or flexible bandwidth RATs may be utilized.

Some embodiments include idle on normal RAT, such as GSM or UMTS. For CScall, for example, GSM or UMTS could be used. With ongoing CS call, ifthere is PS call, GPRS could be used (for DTM UEs) or UMTS could beused. For PS call, PS connection can be transferred to a flexiblebandwidth UTRAN (different mechanisms covered in UE mobility to flexiblebandwidth UTRAN). After PS call is transferred, if there is CS call,fallback to GSM or UMTS could occur.

Some embodiments include idle on a flexible bandwidth RAN, such as aflexible bandwidth UTRAN. When the UE receives a CS call, the UE mayfallback to GSM or UMTS network for example. With ongoing CS call on theflexible bandwidth UTRAN, if a PS call is received, GPRS could be used(for DTM UEs), for example. For PS call received while the UE is on theflexible bandwidth UTRAN, the UE may take the call on the flexiblebandwidth UTRAN. After a PS call, if CS call is received while the UE ison the flexible bandwidth UTRAN, the UE may fallback to GSM, forexample. Other RATs could be utilized in some embodiments.

Some embodiments include transitioning from GSM to flexible bandwidthUMTS. For example, flexible bandwidth UMTS and GSM cells may be servedby the same core network but different RAN networks. Combined GPRS andIMSI Attach may be performed by the UE on the GSM network. The UE may becamping or operating in connected mode on a GSM cell. For CS calls, UEmay stay in GERAN. With ongoing CS call, if there is a MO/MT PS call(DTM UE, for example) UE may stay in GERAN. For PS calls (no ongoing CScall, for example), if requested rate can be served by GPRS/EDGE, UE maystay in GERAN. PS calls (no ongoing CS call, for example), if requestedrate cannot be served by GRPS/EDGE, the UE may be handed over toflexible bandwidth UTRAN. If afterwards, there is MO/MT CS call, UE mayfallback to GSM. In some cases, a UE may be on GSM, GPRS, and/or EDGEfor data and a higher rate of data may be requested.

Turning to FIG. 18A, a communications system 1800-a in accordance withvarious embodiments is shown for a voice central UE is shown asdescribed above. FIG. 18B shows a communications system 1800-b inaccordance with various embodiments for a data centric UE as describedabove. Some embodiments may include determining a preferred radio accesstechnology for a user equipment to camp on based on whether the userequipment is voice centric or data centric. FIG. 18C shows an example ofa communications system 1800-c that may utilize voice centric UEs (e.g.,115-r) and data centric UEs (e.g., 115-s, 115-t). System 1800-c mayinclude one or more co-locate base stations 105-r that may supportmultiple RATs, for example, GSM 900 (with range 106-k), flexiblebandwidth UMTS 900 (with range 106-j), and/or UMTS 2100 (with range106-i).

Some embodiments include a load-based handover from a normal bandwidthsystem to a flexible bandwidth system. FIG. 19A shows a call flow 1900-afor a GERAN to flexible bandwidth UTRAN load-based HO with MO PS inaccordance with various embodiments. FIG. 19B shows a call flow 1900-bfor a GERAN to flexible bandwidth UTRAN load-based HO with MT PS inaccordance with various embodiments. For example, a load-based handovermay be utilized to transition or spring forward from GSM to a flexiblebandwidth UMTS. A UE may camps on the GSM network and may initiate a MOor may receive a MT PS call (with bit rate that can be supported on theflexible bandwidth network but not on GERAN, for example). The UE maysend a service request and may set-up a PDP context for the call. GSMnetwork may accept the calls and may assign appropriate RAB resources tosupport the PS call and may establish a PS connection with the UE. GERANmay decide that the QoS can be served by flexible bandwidth UMTS cell soRAN may initiate a relocation to a flexible bandwidth UTRAN target cellby triggering a load-based handover, for example. The flexible bandwidthUMTS target cell may be determined from a database at the RAN containinga list of geographically overlapping or neighboring UMTS and flexiblebandwidth UMTS cells, for example. GERAN may request that the UE performinter-RAT measurements on the target flexible bandwidth UMTS cell beforeissuing a Cell Change Order command to UE. In some embodiments, this maybe done if UE may not be known to support flexible bandwidth UTRAN. IfUE detects flexible bandwidth UMTS target cell and may report suitablesignal strength to GERAN, GERAN may send a Cell Change order to UTRANcommand to the UE. In case measurements are not issued, GERAN mayblindly send a Cell Change Order command to the UE to tune to thetarget. This may be done if UE is known to support flexible bandwidthUTRAN, for example. In some embodiments, the UE identifies the targetcell before being handed over, which may avoid call drops especially fornon-flexible bandwidth and/or normal UEs.

Some embodiments include a service-based handover from a normalbandwidth system to a flexible bandwidth system. FIG. 20A shows a callflow 2000-a for GERAN to flexible bandwidth UTRAN with service-basedhandover for MO PS in accordance with various embodiments. FIG. 20Bshows a call flow 2000-a for GERAN to flexible bandwidth UTRAN withservice-based handover for MT PS in accordance with various embodiments.For example, a service-based handover may be utilized to transition orspring forward from GSM to a flexible bandwidth UMTS. For example, aredirect of a flexible bandwidth capable UE from GSM to flexiblebandwidth UTRAN may occur when a PS call is attempted by the UE.Service-based HO procedure may be utilized and the UE may be notified ofthe handover with the Cell Change Order message. The Cell Change Order(CCO) message may be sent from the GERAN to the UE regarding theflexible bandwidth UTRAN cell maybe sent after the UE takes measurementon the flexible bandwidth UTRAN cell or blindly by the GERAN. The GERANmight or might not know if UE is flexible before ordering themeasurements or sending the CCO. SGSN, if aware of the UE capability,may selectively perform SBHO for flexible bandwidth capable UEs based onUEIDs such as IMEI. Note that in some embodiments, service-based HO mayinclude the SGSN notifying the BSC to perform a HO to flexible bandwidthUTRAN.

Some embodiments may utilize blind searches and/or UE measurements. Forexample, cell mapping information may be available at RAN from theknowledge of collocated flexible bandwidth and GSM/UMTS cells. UEcapability information may be built up over time by RAN—from previous UEmeasurements reported to RAN, for example. Subsequently, when a UE maybe known to be flexible bandwidth compatible, blind HO may be done (forexample, the CCO is sent to the UE without the network requesting UEmeasurements on the flexible bandwidth UTRAN). Some embodiments includemobile-assisted (UE measurements-based) handover whereby, for example,compressed mode gaps (measurement gaps) may be scheduled forinter-frequency measurements to find a suitable target cell. This may beutilized when a UE may not be known to support flexible bandwidth. Someembodiments utilize database and/or network assisted handover, forexample, which may include no measurements performed on otherfrequencies; rather cell mapping information may be stored in data baseis used to identify the target cell. This approach may be done when UEmay already be known to support flexible bandwidth.

Some embodiments may include transitioning or spring forward from UMTSto flexible bandwidth UMTS. For example, in some scenarios flexiblebandwidth UMTS and UMTS cells may be served by the same core network butdifferent RAN networks. Combined GPRS and IMSI Attach may be performedby the UE on the UMTS network/UTRAN when the UE registers on the UMTScell after which the UE may camp or operate in connected mode on thecell. FIG. 21 shows a communications system 2100 with UMTS to flexiblebandwidth UMTS transition in accordance with various embodiments. The UEmay be assumed to be configured to select UMTS cells for idle modecamping if available. FIG. 22 includes a table 2200 showing differentUMTS to flexible bandwidth UMTS handover scenarios in accordance withvarious embodiments. For example, HO may be triggered by theestablishment of an MT, MO or an existing PS call with QoS demands thatcan be supported by the flexible bandwidth UMTS network. If the UE is inan existing CS call, calls may not be handed over to the flexiblebandwidth UMTS RAN in some cases. In some embodiment, the flexiblebandwidth UMTS network may also support CS so the UE can also be handedover to flexible bandwidth RAN in those cases.

Some embodiments include an inter-frequency handover (IFHO) from anormal bandwidth system to a flexible bandwidth system. FIG. 23A shows acall flow 2300-a for MT PS Call with single RAB IFHO in accordance withvarious embodiments. In some embodiments, if existing PDP context existswhile the UE is in idle, then PDP context activation may not be used asshown in call flow 2300-a. FIG. 23B shows a call flow 2300-b for MO PSCall with single RAB IFHO in accordance with various embodiments. Insome embodiments, if existing PDP context exists while the UE is inidle, then PDP context activation may not be used as shown in call flow2300-b. For example, a UE may camp on the UMTS network and may receive aMT PS call (with bit rate that can be supported on the flexiblebandwidth network) or may decide to establish an MO PS call. In someembodiments, if existing PDP context exists while the UE is in idle,then PDP activation request may not be used sent by the UE. The UE maysend a service request and may set-up a PDP context for the call. UMTSnetwork may accept the calls and may assign appropriate RAB resources tosupport the PS call and may establish a PS connection with the UE. Usinga RAN preference algorithm, the RAN may decide that the QoS can beserved by flexible bandwidth UMTS cell so the RAN may initiate arelocation to a flexible bandwidth UMTS target cell. The flexiblebandwidth UMTS target cell may be determined from a database at the RANcontaining a list of geographically overlapping or neighboring UMTS andflexible bandwidth UMTS cells. In some embodiments, the RAN can requestthat the UE perform inter-frequency measurements on the target cellbefore issuing a handover to UE. If UE finds the target cell and reportsfavorable signal strength to the UMTS RAN, then, the UMTS RAN may send a“physical channel reconfiguration” message to the UE. In casemeasurements are not issued (e.g., blind HO), the UMTS may blindly senda “physical channel reconfiguration” message to the UE to tune to thetarget cell. In some embodiments, the UE identifies the target cellbefore being handed over to avoid call drops especially for non-flexiblebandwidth or normal UMTS UEs.

Some embodiments may include an inter-frequency single RAB handover thatmay be similar to the load-based handover with some differences. Forexample, the inter-frequency HO may be triggered based on the measuredsignal strength of the UE. Once the measured signal strength may be pasta threshold, the UE may signal the event to the UMTS RAN (UTRAN) and therelocation required command may be issued by the RAN to the SGSN. The HOprocedure may proceed similar to the load-based handover. The differencebetween the IFHO and the load-based handover may be that only the UEs(flexible bandwidth UMTS UEs, for example) that can identify theflexible bandwidth UMTS's cell may be triggered to be handed over to thetarget cell.

FIG. 24A shows a call flow 2400-a for MO PS Call scenario involving asingle RAB IFHO in accordance with various embodiments. In this figure,the UE may not be ordered to take cell measurements of the targetflexible bandwidth cell before the handover command is sent in thePhysical Channel Reconfiguration message. FIG. 24B shows a call flow2400-b for MT PSCall scenario involving a single RAB IFHO in accordancewith various embodiments. In this figure, the UE may not be ordered totake cell measurements of the target flexible bandwidth cell before thehandover command is sent in the Physical Channel Reconfigurationmessage. FIG. 24C shows a call flow 2400-c for single RAB IFHO triggeredby UE measurements in inter-RNC scenarios in accordance with variousembodiments. In this figure, similar to FIGS. 24A-24B, the UMTSnetwork/UTRAN and flexible bandwidth UTRAN operate on separate RAN. Thismay illustrate an example of an inter-RNC HO. FIG. 24D shows a call flow2400-d for single RAB IFHO triggered by UE measurements in intra-RNCscenarios in accordance with various embodiments. In this figure, theflexible bandwidth RAN and the WCDMA/UMTS RAN may share the same Radionetwork controller (RNC) but not the same base station. Therefore, afterthe UE measurements may be used to trigger the IFHO, Iub signalling isexchanged between the UMTS Node B and flexible bandwidth UMTS Node B viathe RNC to facilitate resource reservation for the UE on the flexiblebandwidth UMTS Node B. Handover in intra-RNC scenarios are typicallyfaster than those in inter-RNC scenarios.

Some embodiments may include multi-RAB scenarios. For example, in caseof an existing PS call on the UMTS RAN, if another MT or MO PS call maybe received by the network, another RAB might be set-up for such call.As for the single RAB scenario, if flexible bandwidth UMTS cells maysupport the combined multiple RAB service, a load-based handover or aninter-frequency handover may be issued.

FIG. 25 shows a block diagram of a communications system 2500 that maybe configured for utilizing mobility for wireless communications systemsin accordance with various embodiments. This system 2500 may be anexample of aspects of the system 100 depicted in FIG. 1, systems 200 ofFIG. 2, systems 300 of FIG. 3, and/or system 4200 of FIG. 42. The corenetwork 130-e may include memory 2570, and a processor module 2565,which each may be in communication, directly or indirectly, with eachother (e.g., over one or more buses). In some cases, the core network130-e may communicate with other aspects of the network communicationsmodule 2575. System 2500 may be configured to implement differentaspects of the call flows and/or systems as shown in FIGS. 19-24 and/orassociated descriptions.

Core network 130-e may also communicate with radio access networks121-i/121-j 105. Radio access networks 121 may be co-located in somecases, or separated located. In some cases, radio access networks 121may include flexible bandwidth capable radio access networks and/ornormal radio access networks. Radio access networks 121 may be inwireless communication with user equipment 115-j, which may be flexiblebandwidth capable. In some cases, core network 130-e may communicatewith radio access networks 121 utilizing radio access networkcommunication module 2520.

The memory 2570 may include random access memory (RAM) and read-onlymemory (ROM). The memory 2570 may also store computer-readable,computer-executable software code 2571 containing instructions that areconfigured to, when executed, cause the processor module 2565 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 2571 maynot be directly executable by the processor module 2565 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 2565 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 2565 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio.

According to the architecture of FIG. 25, the core network 130-e mayfurther include a radio access communications module 2520. The radioaccess communications module 2520 may manage communications otheraspects of communication, such as communication with user equipment115-j. By way of example, the radio access communications module 2520may be a component of the core network 130-e in communication with someor all of the other components of the core network 130-e via a bus.Alternatively, functionality of the radio access communications module2520 may be implemented as a computer program product, and/or as one ormore controller elements of the processor module 2565 or networkcommunications module 2375.

The components for core network 130-e may be configured to implementaspects discussed above with respect to device 1700 of FIG. 17 and maynot be repeated here for the sake of brevity. The network identificationmodule 1710-a may be an example of the network identification module1710 of FIG. 17. The spring forward module 1715-a may be an example ofthe spring forward module 1715 of FIG. 17. The spring forward module1715-a may include a load-based handover module 2516, a service-basedhandover module 2517, a single RAB inter-frequency handover module 2518,and/or multi-RAB inter-frequency handover module 2519. In some cases,the load-based handover module 2516 may be configured to perform singleRAB load-based handover and/or multi-RAB load-based handover. In somecases, the service-based handover module 2517 may be configured toperform single RAB service-based handover and/or multi-RAB load-basedhandover.

The core network 130-e may also include a handover module 2525 ingeneral that may be utilized to perform handover procedures of the userequipment 115-j from one radio access network 121 to another. Forexample, the handover module 2525 may perform a handover procedure ofthe user equipment 115-j from RAN 121-i to RAN 121-j. The core network130-e may include a redirection module 2521 that may facilitateredirection from one bandwidth system to another.

FIG. 26 shows a block diagram of a communications system 2600 that maybe configured for utilizing mobility for wireless communications systemsin accordance with various embodiments. This system 2600 may be anexample of aspects of the system 100 depicted in FIG. 1, systems 200 ofFIG. 2, systems 300 of FIG. 3, and/or system 4200 of FIG. 42; and/ordevice 1700 of FIG. 17. The radio access network 121-e may includeaspects of a base station 105 and/or a controller 120 to represent acombined system and/or separate components that may comprise part of aradio access network. The base station 105-e may include antennas 2645,a transceiver module 2650, memory 2670, and a processor module 2665,which each may be in communication, directly or indirectly, with eachother (e.g., over one or more buses). The transceiver module 2650 may beconfigured to communicate bi-directionally, via the antennas 2645, withthe user equipment 115-k, which may be a multi-mode user equipment. Thetransceiver module 2650 (and/or other components of the radio accessnetwork 121-e) may also be configured to communicate bi-directionallywith one or more networks. In some cases, the radio access network 121-emay communicate with the core network 130-f through networkcommunications module 2675. Radio access network 121-e may include aneNodeB base station, a Home eNodeB base station, a NodeB base station,and/or a Home NodeB base station. System 2600 may be configured toimplement different aspects of the call flows and/or systems as shown inFIGS. 19-24 and/or associated descriptions.

Radio access network 121-e may also communicate with other base stations105, such as base station 105-m and base station 105-n. Each of the basestations 105 may communicate with user equipment 115-k using differentwireless communications technologies, such as different Radio AccessTechnologies. In some cases, radio access network 121-e may communicatewith other base stations such as 105-m and/or 105-n utilizing basestation communication module 2620. In some embodiments, base stationcommunication module 2620 may provide an X2 interface within an LTEwireless communication technology to provide communication between someof the base stations 105. In some embodiments, radio access network121-e may communicate with other base stations through network 130-f.

The memory 2670 may include random access memory (RAM) and read-onlymemory (ROM). The memory 2670 may also store computer-readable,computer-executable software code 2671 containing instructions that areconfigured to, when executed, cause the processor module 2665 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 2671 maynot be directly executable by the processor module 2665 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 2665 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 2665 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets to the transceiver module2650, and provide indications of whether a user is speaking.Alternatively, an encoder may only provide packets to the transceivermodule 2650, with the provision or withholding/suppression of the packetitself providing the indication of whether a user is speaking.

The transceiver module 2650 may include a modem configured to modulatethe packets and provide the modulated packets to the antennas 2645 fortransmission, and to demodulate packets received from the antennas 2645.While some examples of the radio access network 121-e may include asingle antenna 2645, the radio access network 121-e preferably includesmultiple antennas 2645 for multiple links which may support carrieraggregation. For example, one or more links may be used to support macrocommunications with user equipment 115-k.

According to the architecture of FIG. 26, the radio access network 121-emay further include a base station communications module 2620. The basestation communications module 2620 may manage communications with otherbase stations 105. By way of example, the base station communicationsmodule 2620 may be a component of the radio access network 121-e incommunication with some or all of the other components of the radioaccess network 121-e via a bus. Alternatively, functionality of the basestation communications module 2620 may be implemented as a component ofthe transceiver module 2650, as a computer program product, and/or asone or more controller elements of the processor module 2665.

The components for radio access network 121-e may be configured toimplement aspects discussed above with respect to device 1700 of FIG. 17and may not be repeated here for the sake of brevity. The networkidentification module 1710-b may be an example of the networkidentification module 1710 of FIG. 17. The spring forward module 1715-bmay be an example of the spring forward module 1715 of FIG. 17. Thespring forward module 1715-b may include a load-based handover module2616, a service-based handover module 2617, a single RAB inter-frequencyhandover module 2618, and/or multi-RAB inter-frequency handover module2619. In some cases, the load-based handover module 2616 may beconfigured to perform single RAB load-based handover and/or multi-RABload-based handover. In some cases, the service-based handover module2617 may be configured to perform single RAB service-based handoverand/or multi-RAB load-based handover.

The radio access network 121-e may also include a handover module 2625in general that may be utilized to perform handover procedures of theuser equipment 115-e from radio access network 121-e to another likebase station 105-m. The radio access network 121-e may include aredirection module 2621 that may facilitate redirection from onebandwidth system to another. A scaling module 2627 may be utilized toscale and/or alter chip rates to generate flexible bandwidth waveforms.

In some embodiments, the transceiver module 2650 in conjunction withantennas 2645, along with other possible components of radio accessnetwork 121-e, may transmit information regarding flexible bandwidthwaveforms and/or scaling factors from the radio access network 121-e tothe user equipment 115-k, to other base stations 105-m/105-n, or corenetwork 130-f. In some embodiments, the transceiver module 2650 inconjunction with antennas 2645, along with other possible components ofradio access network 121-e, may transmit information to the userequipment 115-f, to other base stations 105-m/105-n, or core network130-f, such as flexible bandwidth waveforms and/or scaling factors, suchthat these devices or systems may utilize flexible bandwidth waveforms.

FIG. 27 is a block diagram 2700 of a user equipment 115-1 configured formobility in accordance with various embodiments. The user equipment115-1 may have any of various configurations, such as personal computers(e.g., laptop computers, netbook computers, tablet computers, etc.),cellular telephones, PDAs, digital video recorders (DVRs), internetappliances, gaming consoles, e-readers, etc. The user equipment 115-1may have an internal power supply (not shown), such as a small battery,to facilitate mobile operation. In some embodiments, the user equipment115-1 may be the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 23,FIG. 25, FIG. 26, and/or FIG. 42, and/or the device 1700 of FIG. 17. Theuser equipment 115-1 may be a multi-mode user equipment. The userequipment 115-1 may be referred to as a wireless communications devicein some cases. User equipment 115-1 may be configured to implementdifferent aspects of the call flows and/or systems as shown in FIGS.19-24 and/or associated descriptions.

The user equipment 115-1 may include antennas 2740, a transceiver module2750, memory 2780, and a processor module 2770, which each may be incommunication, directly or indirectly, with each other (e.g., via one ormore buses). The transceiver module 2750 is configured to communicatebi-directionally, via the antennas 2740 and/or one or more wired orwireless links, with one or more networks, as described above. Forexample, the transceiver module 2750 may be configured to communicatebi-directionally with base stations 105 of FIG. 1, FIG. 2, FIG. 3,and/or FIG. 26; and/or the radio access networks 121 of FIG. 3B, FIG.25, and/or FIG. 26. The transceiver module 2750 may include a modemconfigured to modulate the packets and provide the modulated packets tothe antennas 2740 for transmission, and to demodulate packets receivedfrom the antennas 2740. While the user equipment 115-1 may include asingle antenna, the user equipment 115-1 will typically include multipleantennas 2740 for multiple links.

The memory 2780 may include random access memory (RAM) and read-onlymemory (ROM). The memory 2780 may store computer-readable,computer-executable software code 2785 containing instructions that areconfigured to, when executed, cause the processor module 2770 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 2785 maynot be directly executable by the processor module 2770 but beconfigured to cause the computer (e.g., when compiled and executed) toperform functions described herein.

The processor module 2770 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 2770 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets to the transceiver module2750, and provide indications of whether a user is speaking.Alternatively, an encoder may only provide packets to the transceivermodule 2750, with the provision or withholding/suppression of the packetitself providing the indication of whether a user is speaking. Theprocessor module 2770 may also include a speech decoder that may performa reverse functionality as the speech encoder.

According to the architecture of FIG. 27, the user equipment 115-1 mayfurther include a communications management module 2760. Thecommunications management module 2760 may manage communications withother user equipment 115. By way of example, the communicationsmanagement module 2760 may be a component of the user equipment 115-1 incommunication with some or all of the other components of the userequipment 115-1 via a bus. Alternatively, functionality of thecommunications management module 2760 may be implemented as a componentof the transceiver module 2750, as a computer program product, and/or asone or more controller elements of the processor module 2770.

The components for user equipment 115-1 may be configured to implementaspects discussed above with respect to device 1700 of FIG. 17 and maynot be repeated here for the sake of brevity. The spring forward module1715-c may be an example of the spring forward module 1715 of FIG. 17.

The user equipment 115-1 may also include a spectrum identificationmodule 2715. The spectrum identification module 2715 may be utilized toidentify spectrum available for flexible bandwidth waveforms. In someembodiments, a handover module 2725 may be utilized to perform handoverprocedures of the user equipment 115-1 from one base station to another.For example, the handover module 2725 may perform a handover procedureof the user equipment 115-1 from one base station to another wherenormal waveforms are utilized between the user equipment 115-1 and oneof the base stations and flexible bandwidth waveforms are utilizedbetween the user equipment and another base station. A scaling module2727 may be utilized to scale and/or alter chip rates to generate/decodeflexible bandwidth waveforms.

In some embodiments, the transceiver module 2750, in conjunction withantennas 2740, along with other possible components of user equipment115-1, may transmit information regarding flexible bandwidth waveformsand/or scaling factors from the user equipment 115-1 to base stations ora core network. In some embodiments, the transceiver module 2750, inconjunction with antennas 2740, along with other possible components ofuser equipment 115-1, may transmit/receive information, such flexiblebandwidth waveforms and/or scaling factors, to/from base stations or acore network such that these devices or systems may utilize flexiblebandwidth waveforms.

Turning to FIG. 28A, a flow diagram of a method 2800-a for providingmobility within wireless communications systems in accordance withvarious embodiments. Method 2800-a may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1, FIG. 3B, FIG. 25, and/orFIG. 26; the radio access networks 121 of FIG. 3B, FIG. 25, and/or FIG.26; the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 25, FIG. 26,FIG. 27, and/or FIG. 42; and/or device 1700 of FIG. 17. Method 2800-bmay implement different aspects of the call flows and/or systems asshown in FIGS. 19-24 and/or associated descriptions.

Block 2810 may include communicating over first radio access network,wherein the first radio access network utilizes a first bandwidthcarrier. Block 2815 may include identifying a second radio accessnetwork, wherein the second radio access network utilizes a firstflexible bandwidth carrier. Block 2820 may include transitioning fromutilizing the first bandwidth carrier of the first radio access networkto utilizing the first flexible bandwidth carrier of the second radioaccess network.

Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may be directed at least in part by acore network. Transitioning from utilizing the first bandwidth carrierof the first radio access network to utilizing the first flexiblebandwidth carrier of the second radio access network may be directed atleast in part by at least one of the radio access networks. The firstbandwidth carrier may include a normal bandwidth carrier or a secondflexible bandwidth carrier different from the first flexible bandwidthcarrier. The first radio access network and the second radio accessnetwork may be shared or may be different.

Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may relate to packet-switchedservices for a user equipment. Transitioning from utilizing the firstbandwidth carrier of the first radio access network to utilizing thefirst flexible bandwidth carrier of the second radio access network mayinclude utilizing a load-based handover. Transitioning from utilizingthe first bandwidth carrier of the first radio access network toutilizing the first flexible bandwidth carrier of the second radioaccess network may include utilizing a service-based handover.Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may include utilizing a blind search.Transitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network may include utilizing a userequipment measurement. Transitioning from utilizing the first bandwidthcarrier of the first radio access network to utilizing the firstflexible bandwidth carrier of the second radio access network mayinclude utilizing a single RAB inter-frequency handover. Transitioningfrom utilizing the first bandwidth carrier of the first radio accessnetwork to utilizing the first flexible bandwidth carrier of the secondradio access network may include utilizing a multi-RAB inter-frequencyhandover. Some embodiments may include utilizing at least a multi-RABload-based handover or a multi-RAB service based handover as part of atleast transitioning from utilizing the first bandwidth carrier of thefirst radio access network to utilizing the first flexible bandwidthcarrier of the second radio access network or identifying the secondradio access network. These techniques may also include utilizing atleast a blind search or a user equipment measurement as part of at leasttransitioning from utilizing the first bandwidth carrier of the firstradio access network to utilizing the first flexible bandwidth carrierof the second radio access network or identifying the second radioaccess network.

In some embodiments, the identification step may perform aspects of thetransitioning steps. Some embodiments may include determining apreferred radio access technology for a user equipment to camp on basedon whether the user equipment is voice centric or data centric.

Turning to FIG. 28B, a flow diagram of a method 2800-b for providingmobility within wireless communications systems in accordance withvarious embodiments. Method 2800-b may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1, FIG. 3B, FIG. 25, and/orFIG. 26; the radio access networks 121 of FIG. 3B, FIG. 25, and/or FIG.26; the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 25, FIG. 26,FIG. 27, and/or FIG. 42; and/or device 1700 of FIG. 17. Method 2800-bmay implement different aspects of the call flows and/or systems asshown in FIGS. 19-24 and/or associated descriptions. In someembodiments, method 2800-b may include aspects of method 2800-a of FIG.28A.

Block 2810-a may include communicating with a user equipment over anormal bandwidth radio access network. Block 2815-a may includeidentifying a flexible bandwidth radio access network. Block 2820-a mayinclude transitioning from utilizing the normal bandwidth radio accessnetwork to utilizing the flexible bandwidth radio access network. Atblock 2525, communication may be established with the user equipmentover the flexible bandwidth radio access network.

Turning to FIG. 28C, a flow diagram of a method 2800-c for providingmobility within wireless communications systems in accordance withvarious embodiments. Method 2800-c may be implemented utilizing variouswireless communications devices and/or systems including, but notlimited to: the core networks 130 of FIG. 1, FIG. 3B, FIG. 25, and/orFIG. 26; the radio access networks 121 of FIG. 3B, FIG. 25, and/or FIG.26; the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 25, FIG. 26,FIG. 27, and/or FIG. 42; and/or device 1700 of FIG. 17. Method 2800-bmay implement different aspects of the call flows and/or systems asshown in FIGS. 19-24 and/or associated descriptions. In someembodiments, method 2800-c may include aspects of method 2800-a of FIG.28A, and/or method 2800-b of FIG. 28B.

Block 2810-b may include communicating with a user equipment over firstradio access network. The first radio access network may utilize a firstbandwidth carrier. Block 2815-b may include identifying a second radioaccess network. The second radio access network may utilize a firstflexible bandwidth carrier. At block 2830, a preferred radio accesstechnology may be determined for the user equipment to connect to basedon whether the user equipment is voice centric or data centric. Block2820-b may include transitioning from utilizing the first bandwidthcarrier of the first radio access network to utilizing the firstflexible bandwidth carrier of the second radio access network utilizingat least a load-based handover, an inter-frequency handover, or aservice-based handover.

Methods, systems, and devices for facilitating mobility between flexiblebandwidth systems and normal bandwidth systems and/or other flexiblebandwidth systems are provided. These methods, systems, and devices mayutilize device 2900 of FIG. 29, system 3800 of FIG. 38, system 3900 ofFIG. 39, user equipment 115 of FIG. 4000, method 4100-a of FIG. 41A,and/or method 4100-b of FIG. 41B, for example. Some examples provide fortransitioning or fallback from flexible bandwidth systems tonon-flexible bandwidth systems that has no support for some or all CSservices (e.g., CS voice), transitioning to other flexible bandwidthsystems, and/or systems that natively support requested circuit-switched(CS) services (e.g., CS voice services) including: transitioning from afirst radio access network to second radio access network, where thefirst radio access network includes a flexible bandwidth radio accessnetwork and the second radio access network includes a normal bandwidthradio access network or another flexible bandwidth system. In oneexample, a method for facilitating mobility for wireless communicationssystems may include: communicating over first radio access network,where the first radio access network utilizes a first flexible bandwidthcarrier; identifying a second radio access network, where the secondradio access network utilizes a second bandwidth carrier; andtransitioning from utilizing the flexible bandwidth carrier of the firstradio access network to utilizing the second bandwidth carrier of thesecond radio access network. This transition may happen betweendifferent radio access technologies (RATs) (e.g., from flexiblebandwidth UTRAN to GERAN) or between the same RATs (e.g., from flexiblebandwidth UTRAN to UTRAN). The UE, network, network elements, orstandard may treat the flexible bandwidth carrier as either the same RATor different RAT or some combination thereof. The second bandwidthcarrier may include a normal bandwidth carrier or another flexiblebandwidth carrier different from the first bandwidth carrier.

A core network may direct one or more aspects of the transitioning. Atleast one of the radio access networks directs one or more aspects ofthe transitioning in some examples. The transitioning may relate tocircuit-switched voices services for a user equipment. The transitioningmay utilize a variety of different procedures including, but not limitedto, a circuit-switched fallback (CSFB)-like procedure, a redirectionprocedure (CN redirection as well as RAN redirection), a cell changeorder procedure, a service-based handover, and/or a tune away procedureby the user equipment.

CSFB may often used to support voice services in a RAT or carrier thatdoes not currently support voice. The user may then “fallback” to a RATor carrier that does support voice. Though CSFB may be mainly used inthe context of voice services, the tools and techniques may begeneralized to any CS services or even any specific set of CS services.Such set may change. For example, the same technique can be used duringa CS video service. Some embodiments may refer to CSFB or CSFB-likeprocedures.

Transitioning from a flexible bandwidth system to a non-flexiblebandwidth system, to another flexible bandwidth system that nativelysupport CS voice services, or to a circuit-switched voice supportingsystem may utilize CSFB-like techniques and procedures. CSFB may not bedefined for UMTS/GSM as UMTS/GSM supports CS voice. Accordingly oneexample of redirection from flexible bandwidth UMTS to UMTS/GSM may bemodeled along the lines of CSFB. CSFB may in general be supported fromLTE to UMTS. Consider, for example, a flexible bandwidth UMTS networkthat may support PS calls or services, while CS calls may be supportedon another network, such as GSM or UMTS. A user equipment may perform ajoint GPRS and IMSI attach during registration prior to initiating acall. While in an ongoing PS call, to answer an incoming CS call, the PScall may be terminated. In some cases, the PS calls may be handed overto the other radio access network or suspended for the duration of theCS call when mobile is redirected to the other radio access network. Tosupport a CS MO call, while the UE is in a PS call on a flexiblebandwidth network, the user equipment may send a MO CS service requestwith an indicator (e.g., “CSFB indicator”) to core network (e.g., SGSN).The “CSFB indicator” may notify the SGSN that the CM service request isnot a regular CS request but one that requires fallback. A flexiblebandwidth RAN, such as a flexible bandwidth UTRAN, may receive a requestfrom the core network (e.g., SGSN) about a possible migration of the UEfrom the current RAT to another RAT, such as GERAN or UTRAN, forexample, to answer the CS call using a RAN redirection request/responseprocedure. The flexible bandwidth UTRAN may receive information such asthe RAT location-area ID (LAI) or PLMN ID from the core network in theRAN redirection request message. The information maybe utilized by theflexible bandwidth RAN to order measurements on the GERAN or UTRAN inorder to find the best cell on the new RAT. With the target cellidentified, an RRC release procedure with a redirection to the GERAN orUTRAN may be initiated to order the UE to migrate to the target cell. Incase some System Information about the target cell is available, theflexible bandwidth RNC may include this information in the redirectionmessage. The PDP context and RABs that were previously used to maintainthe PS connection between the flexible bandwidth RAN and the UE may bereleased at the SGSN. The user equipment may then switch to the new RATusing the system information and send a CS service request on the newcell with a flag (e.g., “CSMO” flag) to indicate CSFB to the MSC. A CSconnection may be set-up on the new RAT, such as GERAN or UTRAN. Asimilar procedure may be followed for MT CS call. Current CM servicerequest message used in UMTS/GSM may not allow the inclusion of “CSFB”indicator or “CSMO” flag, so new messages may be created or existing CMrequest message maybe extended to support this procedure. In addition,the RAN redirection request message may not exist in UMTS; therefore, anew RAN redirection message carrying information such as the RAT,frequency information, etc. may be created or existing messages such asthe RAB assignment messages maybe extended to include this information.The RRC release with redirection message in the current standards maynot carry SI; therefore, new messages may be created or existingmessages may need to be extended.

Some embodiments provide for transitioning from a flexible bandwidthsystem to a non-flexible bandwidth system, to another flexible bandwidthsystem, and/or to a circuit-switched voice supporting system usingCSFB-like procedure as discussed above. However, instead of creating newmessages or extending existing messages, existing messages in UMTS maybe used and the flexible bandwidth UTRAN or flexible bandwidth CoreNetwork entities associated with these messages may determine therelevant information without receiving the information in a message. Forexample, since the UMTS CS service request message may not include the“CSFB” indicator, the SGSN may determine from the reception of the CMservice request message, knowledge of UE capabilities, UE registrationinfo, network capabilities and/or services offered by the network to theUE, if the CM service request should be treated as a CSFB request ornot. Likewise, when the UE sends the CM service request on the new cellwithout the “CSMO” flag, the MSC may make the decision if to treat themessage as a CSFB request or not. Instead of defining a RAN redirectionmessage or extending the RAB messages, the RAB request/response messagecan be used. An optional “LAI” could be sent in the message. The LAIcould be used by the RNC to create database of the RAT and frequencyassociated with that LAI. With the database, once the RAN receives the“LAI” it could predict the corresponding frequency info and RATinformation. However, the RAT and frequency information that could havebeen carried in those messages may be determined by the flexiblebandwidth UTRAN (e.g., the RNC). To minimize the need for including SIin the RRC release with a re-direction message, UE measurements may beordered by the flexible bandwidth UTRAN prior to sending the RRC releasewith a re-direction message to ensure that the UE is being redirected tocell that is already identified. For this purpose, the flexiblebandwidth UTRAN may use the RRC Connection Release with Release cause“preemptive release” and redirection info (e.g., Frequency Info andInter-RAT Info) to terminate the ongoing PS call and order the UE tohandover to the target cell. For the inter-RAT info, currently only GSMRAT information may be included in the RRC Connection Release; amodification may be used to include information for UMTS cells in thismessage.

Some embodiments provide for transitioning from a flexible bandwidthsystem to a non-flexible bandwidth system, to another flexible bandwidthsystem, and/or to a circuit-switched voice supporting system utilizingcell change order commands. In UMTS, for example, inter-RAT mobilityfrom UMTS to GSM in PS domain may be handled using “Cell Change Orderfrom UTRAN” to transfer a PS connection to another RAT (e.g., GPRS) whenthe UE is in RRC states such as the Cell_DCH or Cell_FACH state. In CSdomain, “Handover from UTRAN” may be used. Similarly, inter-RAT mobilityfrom GSM to UMTS in PS domain may be handled using “Cell Change Order toUTRAN” to transfer a PS connection from GSM to UMTS. In CS domain,“Handover to UTRAN” may be used. These tools and techniques may be usedto initiate fallback to UMTS/GSM, possibly as a result of inter-RATmeasurements reported by user equipment indicating the presence of asuitable UMTS/GPRS cell. For example, when the UE has an ongoing PSconnection through the flexible bandwidth UTRAN, the flexible bandwidthRAN may indicate the RABs to be transferred and the information the userequipment may utilize to identify and camp on the GPRS cell to the UE.GSM Info in “Cell Change Order from UTRAN” may include: BSIC, BandIndicator, BCCH ARFCN, and/or NC Mode. The user equipment may attempt toestablish a connection with target GPRS cell and may connect the upperlayer entities corresponding to the indicated RABs to the radioresources offered by the target RAT. If the procedure succeeds, the PSCore Network may inform the flexible bandwidth UTRAN so that theflexible bandwidth UTRAN can release the dedicated resources assigned tothe user equipment (e.g., UTRAN) radio resources and user equipmentcontext information). If the procedure fails, the user equipment maysend a “Cell Change Order From UTRAN” Failure message and may maintainthe connection with flexible bandwidth UTRAN. This example may assumethat there is ongoing PS call in flexible bandwidth UTRAN and then thereis MO/MT CS call which may be redirected to GERAN and PS call may alsobe handed over to GERAN. Similar fallback procedures can be used whenthe UE has existing PS connection through the flexible bandwidth UTRANand receives/transmits a MO/MT voice call. Flexible bandwidth UTRAN maysend “Cell Change Order from UTRAN” for voice fallback to GERAN andbehaves as UTRAN. Flexible bandwidth UTRAN may send “Cell Change Orderto UTRAN” for voice fallback to UTRAN and behaves as if it differentfrom UTRAN.

In some embodiments, transitioning from a flexible bandwidth system to anon-flexible bandwidth system, to another flexible bandwidth system,and/or to a circuit-switched voice supporting system may utilize aservice-based handover. For this procedure, the voice fallback decisionmay be made by the core network entities such as the MSC and respectiveRAN is notified by using the RAB assignment message with a service-basedhandover information element (IE). For example, a Core Network (CN) maybe aware that flexible bandwidth RAN, such as a flexible UTRAN, may notsupport CS voice (network preference). The MSC/CN may be configured toconduct Service Based Handover (SBHO) to GSM, to normal bandwidth UTRANor other network for voice services. For a MT voice call, the MSC maysend Page to the flexible RNC. The flexible bandwidth UMTS RNC may pagethe user equipment and the UMTS RRC connection may be established asneeded. After Direct Transfer messages have been exchanged between userequipment and MSC, the MSC may send a RAB Assignment Request (forexample, indicating handover to GSM may be performed using aService-based Handover IE). The flexible bandwidth UTRAN may send RABAssignment Response message to MSC accepting the handover. The flexiblebandwidth UTRAN may immediately after send Relocation Required messagethrough the MSC to the to the GERAN to reserve resources for the UE.When the flexible RAN receives acknowledge that the GERAN is ready forthe handover, the flexible bandwidth RNC (in the flexible RAN) maynotifies the UE by sending a “Handover from UTRAN” command.

Some embodiments provide for transitioning from a flexible bandwidthsystem to a non-flexible bandwidth system, to another flexible bandwidthsystem, and/or to a circuit-switched voice supporting system utilizingRAN Redirection. For this procedure, the decision to fallback to anothernetwork in order to answer an MT/MO voice call may be made by the RANand communicated to the CN and the UE. This procedure could be used inscenarios where the CN is not aware of whether or not the RAN supportsvoice services. For example, a user equipment may be camping on aflexible bandwith RAN, such as a flexible bandwidth UTRAN. The flexiblebandwidth UTRAN may handle transition or voice fallback without corenetwork (CN) being aware that flexible bandwidth UTRAN may not supportvoice. CN may support CS and PS Attach over flexible bandwidth UTRAN byregistering the user equipment on flexible bandwidth UTRAN LA and RA forboth CS and PS calls. When there is a MO/MT CS voice call, the flexiblebandwidth UTRAN may redirect user equipment to other RANs for reasonssuch as coverage (as if user equipment reached end of coverage area forflexible UTRAN, for example) and/or capacity (as if flexible bandwidthUTRAN's admission control indicates a loaded system, for example). Whenthe CN is notified, the CS call may be transferred to a GERAN or UTRANthrough the MCS, for example. Implementation may be easier if the sameMSC serves the flexible bandwidth UTRAN and GERAN/UTRAN. There may beseveral flavors for implementing the RAN redirection. In one example,the flexible bandwidth UMTS RNC may always reject RAB Assignment requestfrom MSC (for voice, not necessarily for SMS) and may initiate theRelocation Preparation procedure (through the MSC) with a cell on theGERAN/UTRAN. The flexible bandwidth UTRAN may order some UE measurementson cells in the GERAN/UTRAN to identify the target cell for the voicefallback. The rejection in the RAB response message to the MSC mayindicate a message such as“RABs Failed To Setup Or Modify List” or“Relocation required”. When the “RABs Failed To Setup Or Modify List”message is included, possible causes may include “Relocation Triggered”,“Relocation desirable for radio reasons”, “Directed Retry”, “Reduce Loadin Serving Cell”, “Requested Traffic Class not Available”, etc. Possiblecauses when the “Relocation required” message is indicated could be“Time critical Relocation”, “Resource optimization relocation”,“Relocation desirable for radio reasons”, “Directed Retry”, “Reduce Loadin Serving Cell” etc. Once the Relocation procedure is completed andresources are reserved on the target cell for the UE, the flexiblebandwidth user equipment may tune to GERAN/UTRAN and continue thehandover to set-up the CS connection. The Directed Retry mechanism andLoad Based Handover (LBHO) may work for flexible bandwidth UTRAN toGERAN mobility while Inter-Frequency Load Based HO works for flexiblebandwidth UTRAN to UTRAN mobility. In another example flexible bandwidthUMTS user equipment may send RRC Connection Request to flexiblebandwidth UTRAN with Establishment cause and domain type information forto initiate a fallback for an MO/MT CS voice call. In this case, theflexible bandwidth UTRAN may know whether it is originatingconversational call, terminating conversational call and therefore,while set-up the RRC connection, may send a RRC Connection Reject withRedirection Info for CS voice calls only. The Rejection Cause in RRCConnection Reject may be “congestion” or “unspecified”. This example maybe used when there may be no ongoing PS connection, for example.

Transitioning or fallback from a flexible bandwidth system to anon-flexible bandwidth system, to another flexible bandwidth system,and/or to a circuit-switched voice supporting system may utilize atuning away procedure by the user equipment. For example, a userequipment can be idle or connected mode on the flexible bandwidth RAN,such as flexible bandwidth UTRAN that does not support voice services,and may tune away periodically to monitor pages in other RATs e.g. GSMor UMTS. In some cases, the network may send CS pages over GSM or UMTS.The tune away may be with assistance of flexible bandwidth UTRAN whereflexible bandwidth UTRAN may configure compressed mode for userequipment to tune away and monitor pages in GSM or UMTS. The tune awaymay also be without assistance from flexible bandwidth UTRAN, similar tosome implementations in 1x/DO networks. The lack of coordination fromthe flexible bandwidth UTRAN might lead to performance degradation ofthe connection the flexible bandwidth UTRAN if the UE is in connectedmode. This perform penalty for a UE in connected mode on the flexiblesystem may be expected to be more than that of the 1x/DO model becauseof time stretched nature of the flexible system.

Turning next to FIG. 29, a block diagram illustrates a device 2900 thatincludes mobility functionality in accordance with various embodiments.The device 2900 may be an example of aspects of: the core networks 130of FIG. 1, FIG. 3B, FIG. 38, and/or FIG. 39; the radio access networks121 of FIG. 3B, FIG. 38, and/or FIG. 39; and/or the user equipment 115of FIG. 1, FIG. 2, FIG. 3, FIG. 38, FIG. 39, FIG. 40, and/or FIG. 42.The device 2900 may also be a processor. The device 2900 may include areceiver module 2905, a network identification module 2910, a fallbackmodule 2915, and/or a transmitter module 2920. Each of these componentsmay be in communication with each other. Device 2900 may be configuredto implement different aspects of the call flows and/or systems as shownin FIGS. 30-37 and/or associated descriptions.

These components of the device 2900 may, individually or collectively,be implemented with one or more application-specific integrated circuits(ASICs) adapted to perform some or all of the applicable functions inhardware. Alternatively, the functions may be performed by one or moreother processing units (or cores), on one or more integrated circuits.In other embodiments, other types of integrated circuits may be used(e.g., Structured/Platform ASICs, Field Programmable Gate Arrays(FPGAs), and other Semi-Custom ICs), which may be programmed in anymanner known in the art. The functions of each unit may also beimplemented, in whole or in part, with instructions embodied in amemory, formatted to be executed by one or more general orapplication-specific processors.

The receiver module 2905 may receive information such as packet, data,and/or signaling information regarding what device 2900 has received ortransmitted. The received information may be utilized by the networkidentification module 2910 and/or fallback module 2915 for a variety ofpurposes.

In some embodiments, fallback module 2915 is configured fortransitioning from a first radio access network to second radio accessnetwork, where the first radio access network includes a flexiblebandwidth radio access network and the second radio access networkincludes a normal bandwidth radio access network may occur. In someembodiments, a core network may direct one or more aspects of thetransitioning through fallback module 2915. At least one of the radioaccess networks directs one or more aspects of the transitioning throughfallback module 2915 in some embodiments. The transitioning may relateto circuit-switched voices services for a UE. The fallback module 2915may utilize a variety of different procedures including, but not limitedto, a circuit-switched fallback-like procedure, a redirection procedure,a cell change order procedure, a service-based handover, a RANredirection procedure, and/or a tune away procedure by the UE.

Device 2900, through receiver module 2905 and/or transmitter module2902, may be configured for communicating over first radio accessnetwork, wherein the first radio access network utilizes a firstflexible bandwidth carrier. Network identification module 2910 may beconfigured for identifying a second radio access network. The secondradio access network may utilize a first bandwidth carrier. Fallbackmodule 2915 may be configured for transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio accessnetwork.

The fallback module 2915 may be configured such that transitioning fromutilizing the first flexible bandwidth carrier of the first radio accessnetwork to utilizing the first bandwidth carrier of the second radioaccess network may be directed at least in part by a core network.Transitioning from utilizing the first flexible bandwidth carrier of thefirst radio access network to utilizing the first bandwidth carrier ofthe second radio access network may be directed at least in part by atleast one of the radio access networks. At least transitioning fromutilizing the first flexible bandwidth carrier of the first radio accessnetwork to utilizing the first bandwidth carrier of the second radioaccess network or identifying the second radio access network may relateto a call set-up. The first bandwidth carrier may include a normalbandwidth carrier or a second flexible bandwidth carrier.

The network identification module 2910 and/or fallback module 2915 maybe configured such that at least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may relate tocircuit-switched voice services for a user equipment.

The network identification module 2910 and/or fallback module 2915 maybe configured such that at least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing acircuit-switched fallback-like procedure. In some cases, an indicator,which may include a flag, may be utilized to signal the use of thecircuit-switched fallback-like procedure. In other cases, one of theradio access networks or a core network may determine that thecircuit-switched fallback-like procedure is being utilized withreceiving a specific indicator signaling the use of the circuit-switchedfallback-like procedure. At least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing acell change order procedure. At least transitioning from utilizing thefirst flexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing aservice-based handover. At least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing aRAN redirection procedure. At least transitioning from utilizing thefirst flexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing atune away procedure by a user equipment.

Some embodiments of device 2900 may provide mobility between flexiblebandwidth systems to non-flexible bandwidth systems. The non-flexiblebandwidth systems may be configured to handle circuit-switched voiceservices. The mobility between flexible bandwidth systems andnon-flexible bandwidth systems and/or circuit-switched voice-supportingsystems may be referred to as transitioning between these systems and/orvoice fallback. For example, some embodiments may include transitionfrom a flexible bandwidth RAN to a non-flexible bandwidth RAN forcircuit-switched voice services. One example may include voice fallbackfrom a flexible bandwidth RAN to a GERAN, UTRAN, or other radio accesstechnology RAN. In some embodiments, a flexible bandwidth RAN orflexible bandwidth capable UE may also be capable of normal RAN ornormal UE functionality. Thus, a flexible bandwidth RAN or flexiblebandwidth capable UE may be a flexible-capable and normal-capable RAN orUE, respectively.

The transition or fallback procedures may utilize a variety oftechniques in accordance with various embodiments. Different embodimentsmay utilize different techniques for these transitioning and/or fallbackprocedures including, but not limited to, circuit-switched fallback(CSFB)-like procedure with new or modified existing messages, CSFB-likeprocedure using existing messages and modified RAN and/or CN entities,cell change order, service-based handover, RAN redirection, and/or tuneaway by mobile.

Merely by way of example, the following provides several differentexamples utilizing specific radio access technologies. Other similarembodiments may include the use of other RATs. One embodiment includesfallback from flexible UTRAN to GERAN, UTRAN, or 1× using a CircuitSwitched Fallback (CSFB) like procedure with new or modified existingmessages. One embodiment includes fallback from UTRAN to GERAN or UTRANusing CSFB-like procedure with existing messages and modified CN and RANentities. One embodiment includes fallback from flexible bandwidth UTRANto GERAN using Cell Change Order commands. One embodiment includesfallback from flexible UTRAN to GERAN or UTRAN using Service-BasedHandover. Some embodiments include fallback from flexible bandwidthUTRAN to GERAN/UTRAN using RAN Redirection. One embodiment includesfallback from flexible bandwidth UTRAN to GERAN or UTRAN by allowing theUE Tune Away to other RATs.

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system or to acircuit-switched voice supporting system utilizing CSFB like procedurewith new or modified existing messages. FIG. 30A shows a call flow3000-a for a MO CSFB-like procedure to a RAT such as UMTS or GSM. Forexample, CSFB-like procedures may be utilized to transition or fallbackto UMTS or GSM. Merely by way of example, consider a flexible bandwidthUMTS network that may support PS calls or services, while CS calls maybe supported on another network, such as GSM or UMTS. A UE may perform ajoint GPRS and IMSI attach during registration prior to initiating acall. While on an ongoing PS call, to answer an incoming CS call, a PScall may be terminated. In some cases, the PS calls may be PS handoveror suspended. For a CS MO call, a UE may send a MO CS service request“with CSFB indicator” to core network (e.g., SGSN). A flexible bandwidthRAN, such as a flexible bandwidth UTRAN, may receive a request from thecore network (e.g., SGSN) about a possible migration of the UE from thecurrent RAT to another RAT, such as GERAN or UTRAN, for example, toanswer the CS call using a RAN redirection request/response procedure.The flexible bandwidth UTRAN may receive information such as the RAT,LAI, or PLMN ID from the core network in the RAN redirection message.The information may be utilized by the flexible bandwidth RAN to ordermeasurements on the GERAN or UTRAN in order to find the best cell on thenew RAT. With the target cell identified, an RRC release procedure witha redirection to the GERAN or UTRAN may be initiated to order the UE tomigrate to the target cell. In case some System Information about thetarget cell is available, the flexible bandwidth RNC may include thisinformation in the redirection message. The PDP context and RABs thatwere previously used to maintain the PS connection between the flexiblebandwidth RAN and the UE may be released at the SGSN. The user equipmentmay then switch to the new RAT using the System information and send aCS service request on the new cell with a flag (e.g., “CSMO” flag) toindicate CSFB to the MSC. A CS connection may be set-up on the new RAT,such as GERAN or UTRAN.

Some embodiments are configured for CS MT calls utilizing a variety ofdifferent RATs. The following examples may utilize a flexible bandwidthUTRAN, GSM, and/or UMTS, but other RATs may be utilized. FIG. 30B showsa call flow 3000-b for an MT CSFB-like procedure to a RAT, such as UMTSor GSM. For example, an MSC may receive a CS service request for thisUE. The MSC may notify the SGSN that the UE needs to be paged. The SGSNmay notify the UE about the CS call request using a CS notificationmessage (with a paging type 2 on the RAN, for example). UE may send a MTCS service request with the “CSFB indicator” to core network (SGSN inthis case). A flexible bandwidth UTRAN may be notified by the SGSN aboutthe migration to GERAN or UTRAN to answer the CS call using the RANre-direction request/response. The flexible bandwidth UTRAN can ordermeasurements on the GERAN or UTRAN to find the best cell on the new RAT.RRC release procedure may be initiated with a redirection to the GERANor UTRAN and SI may be included in the message if available. The PDPcontext and RABs that were previously used to maintain the pS connectionbetween the RAN and UE may be released at the SGSN. The UE may switchRAT and may send page response on the new cell with “CSMT” flag toindicate CSFB to the MSC. A CS connection may be set-up on the GERAN orUTRAN.

Method 3000-a and/or method 3000-b may include transitioning from aflexible bandwidth system to a non-flexible bandwidth system, to anotherflexible bandwidth system that natively support CS voice services, or toa circuit-switched voice supporting system may utilize CSFB-liketechniques and procedures as discussed above. CSFB may not be definedfor UMTS/GSM as UMTS/GSM supports CS voice. Accordingly one example ofredirection from flexible bandwidth UMTS to UMTS/GSM may be modeledalong the lines of CSFB. CSFB may in general be supported from LTE toUMTS. Consider, for example, a flexible bandwidth UMTS network that maysupport PS calls or services, while CS calls may be supported on anothernetwork, such as GSM or UMTS. A user equipment may perform a joint GPRSand IMSI attach during registration prior to initiating a call. While inan ongoing PS call, to answer an incoming CS call, the PS call may beterminated. In some cases, the PS calls may be handed over to the otherradio access network or suspended for the duration of the CS call whenmobile is redirected to the other radio access network. To support a CSMO call, while the UE is in a PS call on a flexible bandwidth network,the user equipment may send a MO CS service request with an indicator(e.g., “CSFB indicator”) to core network (e.g., SGSN). The “CSFBindicator” may notify the SGSN that the CM service request is not aregular CS request but one that requires fallback. A flexible bandwidthRAN, such as a flexible bandwidth UTRAN, may receive a request from thecore network (e.g., SGSN) about a possible migration of the UE from thecurrent RAT to another RAT, such as GERAN or UTRAN, for example, toanswer the CS call using a RAN redirection request/response procedure.The flexible bandwidth UTRAN may receive information such as the RATlocation-area ID (LAI) or PLMN ID from the core network in the RANredirection request message. The information maybe utilized by theflexible bandwidth RAN to order measurements on the GERAN or UTRAN inorder to find the best cell on the new RAT. With the target cellidentified, an RRC release procedure with a redirection to the GERAN orUTRAN may be initiated to order the UE to migrate to the target cell. Incase some System Information about the target cell is available, theflexible bandwidth RNC may include this information in the redirectionmessage. The PDP context and RABs that were previously used to maintainthe PS connection between the flexible bandwidth RAN and the UE may bereleased at the SGSN. The user equipment may then switch to the new RATusing the infotand send a CS service request on the new cell with a flag(e.g., “CSMO” flag) to indicate CSFB to the MSC. A CS connection may beset-up on the new RAT, such as GERAN or UTRAN. A similar procedure maybe followed for MT CS call.

Call flows 3000-a and/or 3000-b may include some embodiments which mayutilize additional messages in UTRAN/GERAN to implement this CSFB-likeprocedure. Some embodiments may modify existing messages by defining newIEs. Current CM service request message used in UMTS/GSM may not allowthe inclusion of “CSFB” indicator or “CSMO” flag, so new messages may becreated or existing CM request message maybe extended to support thisprocedure. In addition, the RAN redirection request message may notexist in UMTS; therefore, a new RAN redirection message carryinginformation such as the RAT, frequency information, etc. may be createdor existing messages such as the RAB assignment messages maybe extendedto include this information. The RRC release with redirection message inthe current standards may not carry SI; therefore, new messages may becreated or existing messages may need to be extended. For example, anadditional IE may be added to the CM service request to indicate voicefallback or transitional mode CM service request. Additional IEs may beadded to the page response to indicate “CSMT flag”. A new message “RANredirection request/response” or similar message may be utilized tocarry information like the LAI, PLMN, and/or RAT information from theSGSN to the flexible bandwidth UTRAN or other flexible bandwidth RAN.This message may be an existing RAB assignment request/response messagewith additional IEs. Additional IEs may include UMTS cells in the RRCrelease with re-direction message. Addition IEs carrying SI may also beincluded in the RRC release with redirection messages to provide SIabout the target cell to the UE.

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system and/or to acircuit-switched voice supporting system utilizing CSFB-like procedurewith currently existing messages (CEM). For example, CSFB with CEMtechniques may be utilized to transition or fallback to UMTS or GSM froma flexible bandwidth UTRAN. In this example, the flexible bandwidthUTRAN may supports PS, while CS calls may be supported on GSM and/orUMTS UE may perform a joint GPRS and IMSI attach during registration. Toanswer the CS call, the PS call may be terminated, handed over orsuspended. For MO calls, the flexible bandwidth UMTS capable UE (when UEis in PS call, for example) may send CM Service Request for “Originatingconversational voice call” for a CS voice call. In some cases, since theUMTS CS service request message may not include the “CSFB” indicator,the SGSN may determine from the reception of the CM service requestmessage, knowledge of UE capabilities, UE registration info, networkcapabilities and/or services offered by the network to the UE, if the CMservice request should be treated as a CSFB request or not. Likewise,when the UE sends the CM service request on the new cell without the“CSMO” flag, the MSC may make the decision if to treat the message as aCSFB request or not. Instead of defining a RAN redirection message orextending the RAB messages, the RAB request/response message can beused. An optional “LAI” could be sent in the message. The LAI could beused by the RNC to create database of the RAT and frequency associatedwith that LAI. With the database, once the RAN receives the “LAI” itcould predict the corresponding frequency info and RAT information.However, the RAT and frequency information that could have been carriedin those messages may be determined by the flexible bandwidth UTRAN(e.g., the RNC). To minimize the need for including SI in the RRCrelease with a re-direction message, UE measurements may be ordered bythe flexible bandwidth UTRAN prior to sending the RRC release with are-direction message to ensure that the UE is being redirected to cellthat is already identified. For this purpose, the flexible bandwidthUTRAN may use the RRC Connection Release with Release cause “preemptiverelease” and redirection info (e.g., Frequency Info and Inter-RAT Info)to terminate the ongoing PS call and order the UE to handover to thetarget cell. For the inter-RAT info, currently only GSM RAT informationmay be included in the RRC Connection Release; a modification may beused to include information for UMTS cells in this message. This mayalso be applicable to method 3100-a through method 3100-b and otherportions discussed below.

Some embodiments provide for MO CS calls with CEM. FIG. 31A shows a callflow 3100-a for an MO CS call with CEM in accordance with variousembodiments. For example, to terminate the ongoing PS call and instructthe UE to move to the GERAN/UTRAN to proceed with the CS call, aflexible bandwidth UTRAN may send the RRC Connection Release withRelease cause “preemptive release” and/or redirection info (e.g.,Frequency Info and Inter-RAT info) to the UE. The GSM RAT informationmay easily be included in the existing RRC connection Release message;some embodiments include a modification to the message to includeinformation for UMTS cells. A flexible bandwidth UMTS UE may send RRCConnection Release Complete. The flexible bandwidth UMTS UE may tune toGSM or WCDMA (or other RAT) frequency as indicated in the redirectioninfo (e.g., Frequency Info and Inter-RAT info). The flexible bandwidthUMTS UE may send a CS service request to the target UMTS or GSM cell andthe corresponding MSC may need to determine that the CS call was forfallback call. The flexible bandwidth UMTS UE may proceed with CS callin GSM or UMTS (or other RAT). The PS data session may be also eithersuspended or transferred.

Some embodiments provide for MT CS calls with CEM. FIG. 31B shows anexample of a call flow 3100-b for an MT CS call with CEM in accordancewith various embodiments. For example, a flexible bandwidth RAN, such asa flexible bandwidth UTRAN, may send a Paging Type 2 to a flexiblebandwidth capable UE, such as UMTS UE (in PS call) with paging cause“Terminating conversational voice call” and CN domain identity “CSdomain” for CS voice call. The flexible bandwidth UMTS UE (in PS call,for example) may respond back with a CM Service Request message. The MSCmay determine that the call requires fallback and may send a RABassignment request message to flexible bandwidth UTRAN with the LAIoptional field included. The flexible bandwidth UTRAN may determinecandidate RAT and frequency information from LAI. The flexible bandwidthUTRAN can initiate measurements on the UTRAN or GERAN cell, for example,such that the UE can identify the cell. The flexible bandwidth UTRAN maysend RRC Connection Release with Release cause “preemptive release”and/or redirection info (e.g., Frequency Info and Inter-RAT info) toterminate the ongoing PS call, for example.

In some cases, the flexible bandwidth UMTS UE sends RRC ConnectionRelease Complete to another flexible bandwidth RAN, such as a flexiblebandwidth UTRAN. The UMTS UE may tune to GSM or UMTS frequency, forexample, as may be indicated in and redirection info (e.g., FrequencyInfo and Inter-RAT info). The flexible bandwidth UMTS UE may respond topaging for MT CS voice call in GSM or UMTS, for example. The PS datasession may be suspended or transferred.

Embodiments that utilize CEM may include normal CM service requestwithout “Fallback indicator” or the “CSMO” flag being used; the SGNSand/or MSC may determine a fallback service request from regular servicerequest using UE registration information. The RNC may determinate thetarget cell RAT and/or frequency from the LAI the RAB Assignment Requestmessage. Some embodiments may include additional IE to provide forredirection to UMTS cells.

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system and/or to acircuit-switched voice supporting system utilizing cell change ordercommands. For example, some embodiments utilize cell change order fromUTRAN. In UMTS, for example, inter-RAT mobility in PS domain may behandled using “Cell Change Order from UTRAN” to transfer a PS connection(UE in Cell_DCH or Cell_FACH state, for example) to another RAT (e.g.,GPRS). In CS domain, “Handover from UTRAN” may be used. These tools andtechniques may be used to initiate by UTRAN, possibly as result ofinter-RAT measurements reported by UE indicating the presence of asuitable GPRS cell. The UTRAN may indicate the RABs to be transferredand the information the UE may utilize to identify and camp on the GPRScell. GSM Info in “Cell Change Order from UTRAN” may include: BSIC, BandIndicator, BCCH ARFCN, and/or NC Mode. The UE may attempt to establish aconnection with target GPRS cell and may connect the upper layerentities corresponding to the indicated RABs to the radio resourcesoffered by the target RAT. If the procedure succeeds, the PS CoreNetwork may inform UTRAN so that UTRAN can release the dedicatedresources assigned to the UE (UTRAN radio resources and UE contextinformation). If the procedure fails, the UE may send a Cell ChangeOrder From UTRAN Failure message and may maintain the connection withUTRAN.

For example, as discussed above, in UMTS, inter-RAT mobility from UMTSto GSM in PS domain may be handled using “Cell Change Order from UTRAN”to transfer a PS connection to another RAT (e.g., GPRS) when the UE isin RRC states such as the Cell_DCH or Cell_FACH state. In CS domain,“Handover from UTRAN” may be used. Similarly, inter-RAT mobility fromGSM to UMTS in PS domain may be handled using “Cell Change Order toUTRAN” to transfer a PS connection from GSM to UMTS. In CS domain,“Handover to UTRAN” may be used. These tools and techniques may be usedto initiate fallback to UMTS/GSM, possibly as a result of inter-RATmeasurements reported by user equipment indicating the presence of asuitable UMTS/GPRS cell. For example, when the UE has an ongoing PSconnection through the flexible bandwidth UTRAN, the flexible bandwidthRAN may indicate the RABs to be transferred and the information the userequipment may utilize to identify and camp on the GPRS cell to the UE.GSM Info in “Cell Change Order from UTRAN” may include: BSIC, BandIndicator, BCCH ARFCN, and/or NC Mode. The user equipment may attempt toestablish a connection with target GPRS cell and may connect the upperlayer entities corresponding to the indicated RABs to the radioresources offered by the target RAT. If the procedure succeeds, the PSCore Network may inform the flexible bandwidth UTRAN so that theflexible bandwidth UTRAN can release the dedicated resources assigned tothe user equipment (e.g., UTRAN) radio resources and user equipmentcontext information). If the procedure fails, the user equipment maysend a “Cell Change Order From UTRAN” Failure message and may maintainthe connection with flexible bandwidth UTRAN. This example may assumethat there is ongoing PS call in flexible bandwidth UTRAN and then thereis MO/MT CS call which may be redirected to GERAN and PS call may alsobe handed over to GERAN. Similar fallback procedures can be used whenthe UE has existing PS connection through the flexible bandwidth UTRANand receives/transmits a MO/MT voice call. Flexible bandwidth UTRAN maysend “Cell Change Order from UTRAN” for voice fallback to GERAN andbehaves as UTRAN. Flexible bandwidth UTRAN may send “Cell Change Orderto UTRAN” for voice fallback to UTRAN and behaves as if it differentfrom UTRAN.

In some cases, instead of triggering “Cell Change Order from UTRAN”based on UE measurements indicating suitable GPRS cells, a flexiblebandwidth UTRAN may send “Cell Change Order from UTRAN” if there is a MOor MT CS voice call for voice fallback from flexible bandwidth UTRAN toGERAN. For MO voice call, UE may send CM Service Request/Setup and thatcan trigger “Cell Change Order from UTRAN”. For MT CS voice call, pagingtype 2 message sent from UTRAN and/or CS Service Request may trigger“Cell Change Order from UTRAN”.

Some embodiments include inter-system cell change order to UTRAN. Thisprocedure may be used by the other RATs (e.g., GSM, GPRS) to command UEto move to the UTRAN Cell using procedures specific for that RAT. Someembodiments include identity of the target UTRAN cell. In UTRAN, the UEmay initiate RRC connection establishment procedure with establishmentcause set to “Inter-RAT Cell Change Order”, for example.

Some embodiments provide for transitioning and/or voice fallback toUMTS. In some cases, instead of triggering “Cell Change Order to UTRAN”based on UE measurements indicating suitable UMTS cells, a flexiblebandwidth UTRAN may send “Cell Change Order to UTRAN” if there is a MOor MT CS voice call for voice fallback from Fractional UTRAN to UTRANFor MO voice call, UE may send CM Service Request/Setup and that maytrigger “Cell Change Order from UTRAN”. For MT CS voice call, pagingtype 2 message sent from UTRAN and/or CS Service Request may trigger“Cell Change Order from UTRAN”, for example.

For some embodiments, flexible bandwidth UTRAN may send “Cell ChangeOrder from UTRAN” for voice fallback to GERAN. In this case, it maybehave as if the flexible bandwidth UTRAN may be identical to UTRAN. Insome embodiments, the flexible bandwidth UTRAN sends “Cell Change Orderto UTRAN” for voice fallback to UTRAN. In this case, it may behave as ifFractional UTRAN is different from UTRAN.

Some embodiments utilizing cell change order involve one or more MOscenarios. FIG. 32A shows an example of a call flow 3200-a of an MOscenario in accordance with various embodiments. For example, a corenetwork may be unaware that a flexible bandwidth UTRAN does not supportCS voice services. The flexible bandwidth capable UE may send CM ServiceRequest to MSC, for example. The MSC may send RAB Assignment Requestindicating handover to GSM should be performed in Service Handover IE,for example. In other cases, the flexible bandwidth UTRAN may decide toHO to GSM based on prior UE measurements or information about voicesupport at the flexible bandwidth RAN. The flexible bandwidth UTRAN maysend RAB Assignment Response message to MSC and may immediately aftersend Relocation Required message to GERAN through the MSC to start thehandover preparation procedures. After the GERAN acknowledges reservingresources for the UE relocation, the flexible bandwidth RNC may send a“Cell Change Order from UTRAN” command with “GSM Info” to UE. If thetarget cell is in the UTRAN, the “Cell Change Order to UTRAN” message isused and “UMTS cell Info” may be added to the message. The Core Networkmay let the flexible UTRAN know that PS call may have been transferred.Once the PS connection is transferred and the UE accesses the targetcell, the CS connection can be established so that the UE then has a CSconnection concurrently with a PS connection. After the flexiblebandwidth UTRAN may release the dedicated resources assigned to the UE(radio resources and/or UE context information, for example).

Some embodiments utilizing cell change order involve one or more MTscenarios. FIG. 32B shows an example of a call flow 3200-b for an MTscenario in accordance with various embodiments. For a MT voice call,for example, the MSC may send Page to a flexible bandwidth RNC. Theflexible bandwidth RNC may page the UE and UE may send CM ServiceRequest. The MSC may send RAB Assignment Request to the flexiblebandwidth RAN based on information. The flexible bandwidth UTRAN maysend RAB Assignment Response message to MSC and may immediately aftersend Relocation Required message to MSC. The MSC may initiate flexiblebandwidth UTRAN to GERAN handover and flexible bandwidth RNC may sendCell Change Order from/to UTRAN command to UE with “GSM Info”. “UMTSInfo” may be added in some cases. The Core Network may let flexiblebandwidth UTRAN know that PS call may have been transferred. Theflexible bandwidth UTRAN may release the dedicated resources assigned tothe UE (radio resources and/or UE context information, for example).

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system and/or to acircuit-switched voice supporting system utilizing service-basedhandover. For example, a CN may be aware that flexible bandwidth RAN,such as a flexible bandwidth UTRAN, may not support native voice(network preference). The MSC/CN may be configured to conduct SBHO toGSM (Service Based Handover) or other network for voice services. For aMT voice call, the MSC may send Page to the flexible bandwidth RNC. Theflexible bandwidth UMTS RNC may page the UE and the RRC connection maybe established as needed. After Direct Transfer message have beenexchanged between UE and MSC, the MSC may send RAB Assignment Request(indicating handover to GSM may be performed in Service Handover IE).Flexible bandwidth UTRAN may send RAB Assignment Response message to MSCand may immediately after send Relocation Required message to MSC. MSCmay initiate flexible bandwidth UTRAN to GERAN handover and flexiblebandwidth RNC sends Handover from UTRAN command to UE. As discussedabove, for SBHO procedures, the voice fallback decision may be made bythe core network entities such as the MSC and respective RAN is notifiedby using the RAB assignment message with a service-based handoverinformation element (IE). For example, a Core Network (CN) may be awarethat flexible bandwidth RAN, such as a flexible UTRAN, may not supportCS voice (network preference). The MSC/CN may be configured to conductService Based Handover (SBHO) to GSM, to normal bandwidth UTRAN or othernetwork for voice services. For a MT voice call, the MSC may send Pageto the flexible RNC. The flexible bandwidth UMTS RNC may page the userequipment and the UMTS RRC connection may be established as needed.After Direct Transfer messages have been exchanged between userequipment and MSC, the MSC may send a RAB Assignment Request (forexample, indicating handover to GSM may be performed using aService-based Handover IE). The flexible bandwidth UTRAN may send RABAssignment Response message to MSC accepting the handover. The flexiblebandwidth UTRAN may immediately after send Relocation Required messagethrough the MSC to the to the GERAN to reserve resources for the UE.When the flexible RAN receives acknowledge that the GERAN is ready forthe handover, the flexible bandwidth RNC (in the flexible RAN) maynotifies the UE by sending a “Handover from UTRAN” command.

In some cases, there may be no equivalent SBHO for flexible bandwidthUTRAN to UTRAN. FIG. 33 shows an example of a call flow 3300 forflexible bandwidth UTRAN to GERAN SBHO (for MT CS). Similar call flowsmay be utilized for MO CS SBHO to GSM may work for CS voice callstypically for existing networks. SMS and/or CS Data may be supported onflexible bandwidth UTRAN. SBHO may typically be exercised when there isno PS connection. With ongoing PS connection, multi RAB call setup maytypically be done on UMTS. The behavior for the flexible bandwidth UTRANmay be changed.

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system and/or to acircuit-switched voice supporting system utilizing RAN Redirection. Forexample, a UE may be camping on a flexible bandwidth RAN, such as aflexible bandwidth UTRAN. The flexible bandwidth UTRAN may handletransition or voice fallback without core network (CN) being aware thatflexible bandwidth UMTS may not support voice. CN may support CS+PSAttach over flexible bandwidth UTRAN by registering the UE on flexiblebandwidth UTRAN LA and RA for both CS and PS calls. When there is MO/MTCS voice call, flexible bandwidth UTRAN may redirect UE to other RANsfor coverage (as if UE reached end of coverage area for flexiblebandwidth UTRAN, for example) and/or capacity (as if flexible bandwidthUTRAN's admission control kicks in, for example). At the CN, the CS callmay be transferred to the MSC supporting the GSM or UMTS, for example.Implementation may be easier if the same MSC serves the flexiblebandwidth UTRAN and GSM or UMTS networks. It may be abstracted at thatflexible bandwidth UTRAN may not support CS voice.

As discussed above, for RAN redirection procedures, the decision tofallback to another network in order to answer an MT/MO voice call maybe made by the RAN and communicated to the CN and the UE. This procedurecould be used in scenarios where the CN is not aware of whether or notthe RAN supports voice services. For example, a user equipment may becamping on a flexible bandwith RAN, such as a flexible bandwidth UTRAN.The flexible bandwidth UTRAN may handle transition or voice fallbackwithout core network (CN) being aware that flexible bandwidth UTRAN maynot support voice. CN may support CS and PS Attach over flexiblebandwidth UTRAN by registering the user equipment on flexible bandwidthUTRAN LA and RA for both CS and PS calls. When there is a MO/MT CS voicecall, the flexible bandwidth UTRAN may redirect user equipment to otherRANs for reasons such as coverage (as if user equipment reached end ofcoverage area for flexible UTRAN, for example) and/or capacity (as ifflexible bandwidth UTRAN's admission control indicates a loaded system,for example). When the CN is notified, the CS call may be transferred toa GERAN or UTRAN through the MCS, for example. Implementation may beeasier if the same MSC serves the flexible bandwidth UTRAN andGERAN/UTRAN. There may be several flavors for implementing the RANredirection. In one example, the flexible bandwidth UMTS RNC may alwaysreject RAB Assignment request from MSC (for voice, not necessarily forSMS) and may initiate the Relocation Preparation procedure (through theMSC) with a cell on the GERAN/UTRAN. The flexible bandwidth UTRAN mayorder some UE measurements on cells in the GERAN/UTRAN to identify thetarget cell for the voice fallback. The rejection in the RAB responsemessage to the MSC may indicate a message such as“RABs Failed To SetupOr Modify List” or “Relocation required”. When the “RABs Failed To SetupOr Modify List” message is included, possible causes may include“Relocation Triggered”, “Relocation desirable for radio reasons”,“Directed Retry”, “Reduce Load in Serving Cell”, “Requested TrafficClass not Available”, etc. Possible causes when the “Relocationrequired” message is indicated could be “Time critical Relocation”,“Resource optimization relocation”, “Relocation desirable for radioreasons”, “Directed Retry”, “Reduce Load in Serving Cell” etc. Once theRelocation procedure is completed and resources are reserved on thetarget cell for the UE, the flexible bandwidth user equipment may tuneto GERAN/UTRAN and continue the handover to set-up the CS connection.The Directed Retry mechanism and Load Based Handover (LBHO) may work forflexible bandwidth UTRAN to GERAN mobility while Inter-Frequency LoadBased HO works for flexible bandwidth UTRAN to UTRAN mobility. Inanother example flexible bandwidth UMTS user equipment may send RRCConnection Request to flexible bandwidth UTRAN with Establishment causeand domain type information for to initiate a fallback for an MO/MT CSvoice call. In this case, the flexible bandwidth UTRAN may know whetherit is originating conversational call, terminating conversational calland therefore, while set-up the RRC connection, may send a RRCConnection Reject with Redirection Info for CS voice calls only. TheRejection Cause in RRC Connection Reject may be “congestion” or“unspecified”. This example may be used when there may be no ongoing PSconnection, for example.

In some embodiments, an MSC may send RAB Assignment Request for CS voicecall in. A RNC may reject RAB Assignment from MSC (for voice, notnecessarily for SMS, for example) and may initiate the RelocationPreparation procedure. Cause for “RABs Failed To Setup Or Modify List”may be Relocation Triggered, Relocation desirable for radio reasons,Directed Retry, Reduce Load in Serving Cell, Requested Traffic Class notAvailable etc. Cause for Relocation Required may be “Time criticalRelocation”, “Resource optimisation relocation”, “Relocation desirablefor radio reasons”, “Directed Retry”, “Reduce Load in Serving Cell”,etc. A flexible bandwidth capable UE may tune to GSM or UMTS frequency,for example, and may respond to page.

Some embodiments may provide different options for the above RANredirection approach. For example, some embodiments include directedretry (flexible bandwidth UTRAN to GSM, for example). Some embodimentsinclude load-based options including, but not limited to, load-basedhandover (flexible bandwidth UTRAN to GERAN, for example) and/orinter-frequency load-based HO (flexible bandwidth UTRAN to UMTS, forexample). These embodiments may work for CS voice calls typically forexisting networks. SMS and CS Data may be supported on the flexiblebandwidth UTRAN. These embodiments may be exercised when there is no PSconnection, though some may be exercised when there is a PSC connection.With ongoing PS connection, multi RAB call setup may be done on UMTS.Behavior for flexible bandwidth UTRAN may be changed. FIG. 34 shows anexample of a call flow 3400 for a flexible bandwidth UTRAN to GERANutilizing directed retry for establishing an MT CS in accordance withvarious embodiments. FIG. 35A shows an example of a call flow 3500-a fora flexible bandwidth UTRAN to GERAN utilizing a load-based handover forestablishing an MT CS in accordance with various embodiments. FIG. 35Bshows an example of a call flow 3500-b in accordance with variousembodiments. In call flows 1800, the RNC may send Relocation Requiredwith cause value “Reduce Load in Serving Cell” etc. (e.g., “Timecritical Relocation”, “Resource optimization relocation”, “Relocationdesirable for radio reasons”, “Directed Retry”, “Reduce Load in ServingCell”, “Access Restricted Due to Shared Networks”, “No Iu CS UPrelocation”). FIG. 36A shows an example of a call flow 3600-a inaccordance with various embodiments. FIG. 36B shows an example of a callflow 3600-b in accordance with various embodiments. FIG. 36C shows anexample of a call flow 3600-c in accordance with various embodiments. Insome embodiments, the RNC sends Relocation Required with cause value“Reduce Load in Serving Cell” etc. Some embodiments may be treated asinter-frequency hard HO between two UMTS frequencies or Inter-RAT HO toUTRAN.

Some embodiments utilize other RAN redirection approaches. For example,a UE may send an RRC Connection Request to flexible bandwidth RAN, suchas a flexible bandwidth UTRAN. RRC Connection Request may haveEstablishment cause and domain type information. The flexible bandwidthUTRAN may know whether it is originating conversational call,terminating conversational call. The flexible bandwidth UTRAN may sendRRC Connection Reject with Redirection Info for CS voice calls only.Rejection Cause in RRC Connection Reject may be congestion orunspecified. Some embodiments may be used when there is no ongoing PSconnection, though there may be an ongoing PS connection in some cases.Some embodiments that include RAN redirection may include RedirectionInfo that may contain inter-RAT info; this may define target system forredirected cell selection (i.e., GSM). From Rel 6 onwards, cell specificinformation may be provided for target system. Some embodiments mayinclude Redirection Info that may contain frequency information. Some ofthese embodiments may be treated as inter-frequency redirection. FIG.37A shows an example of a call flow 3700-a for a RAN redirectionapproach (MO) in accordance with various embodiments. FIG. 37B shows anexample of a call flow 3700-b for a RAN redirection approach (MT) inaccordance with various embodiments.

Some embodiments provide for transitioning or fallback from a flexiblebandwidth system to a non-flexible bandwidth system and/or to acircuit-switched voice supporting system utilizing tune away by the UE.For example, a UE can be idle or connected in flexible bandwidth RAN,such as flexible bandwidth UTRAN, and may tune away periodically tomonitor pages in GSM or UMTS, for example. In some cases, the networkmay send CS pages over GSM or UMTS. The tune away may be with assistanceof flexible bandwidth UTRAN where flexible bandwidth UTRAN may configurecompressed mode for UE to tune away and monitor pages in GSM or UMTS.The tune away may also be without assistance from flexible bandwidthUTRAN, like 1x/DO model. Hit in connected mode for the flexiblebandwidth system may be more than 1x/DO model as time may be stretchedin flexible bandwidth system. The flexible bandwidth capable UEimplementation may handle the voice fallback without RAN Redirection orHandover in some cases.

Furthermore, as discussed above, for these tune away procedures, a userequipment can be idle or connected mode on the flexible bandwidth RAN,such as flexible bandwidth UTRAN that does not support voice services,and may tune away periodically to monitor pages in other RATs e.g. GSMor UMTS. In some cases, the network may send CS pages over GSM or UMTS.The tune away may be with assistance of flexible bandwidth UTRAN whereflexible bandwidth UTRAN may configure compressed mode for userequipment to tune away and monitor pages in GSM or UMTS. The tune awaymay also be without assistance from flexible bandwidth UTRAN, similar tosome implementations in 1x/DO networks. The lack of coordination fromthe flexible bandwidth UTRAN might lead to performance degradation ofthe connection the flexible bandwidth UTRAN if the UE is in connectedmode. This perform penalty for a UE in connected mode on the flexiblesystem may be expected to be more than that of the 1x/DO model becauseof time stretched nature of the flexible system.

FIG. 38 shows a block diagram of a communications system 3800 that maybe configured for utilizing mobility for wireless communications systemsin accordance with various embodiments. This system 3800 may be anexample of aspects of the system 100 depicted in FIG. 1, systems 200 ofFIG. 2, systems 300 of FIG. 3, and/or system 4200 of FIG. 42. The corenetwork 130-g may include memory 3870, and a processor module 3865,which each may be in communication, directly or indirectly, with eachother (e.g., over one or more buses). In some cases, the core network130-g may communicate with other aspects of the network communicationsmodule 3875. System 3800 may be configured to implement differentaspects of the call flows and/or systems as shown in FIGS. 30-37 and/orassociated descriptions.

Core network 130-g may also communicate with radio access networks121-i/121-j 105. Radio access networks 121 may be co-located in somecases, or separated located. In some cases, radio access networks 121may include flexible capable radio access networks and/or normal radioaccess networks. Radio access networks 121 may be in wirelesscommunication with user equipment 115-m, which may be flexible capable.In some cases, core network 130-g may communicate with radio accessnetworks 121 utilizing radio access network communication module 3820.Radio access networks 121 may include aspects of base stations 105and/or controllers 120 as show in the other figures.

The memory 3870 may include random access memory (RAM) and read-onlymemory (ROM). The memory 3870 may also store computer-readable,computer-executable software code 3871 containing instructions that areconfigured to, when executed, cause the processor module 3865 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 3871 maynot be directly executable by the processor module 3865 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 3865 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 3865 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets, and provide indicationsof whether a user is speaking. The processor module 3865 may alsoinclude a speech decoder that may perform a reverse functionality as thespeech encoder.

According to the architecture of FIG. 38, the core network 130-g mayfurther include a RAN communications module 3820. The RAN communicationsmanagement module 3820 may manage communications other aspects ofcommunication, such as communication with user equipment 115-m and/orRANs 121-i/121-j. By way of example, the RAN communications module 3820may be a component of the core network 130-g in communication with someor all of the other components of the core network 130-g via a bus.Alternatively, functionality of the RAN communications module 3820 maybe implemented as a computer program product, and/or as one or morecontroller elements of the processor module 3865.

The components for core network 130-g may be configured to implementaspects discussed above with respect to device 2900 in FIG. 29 and/ordevice 2200 of FIG. 22 and may not be repeated here for the sake ofbrevity. The network identification module 2910-a may be an example ofthe network identification module 2900 of FIG. 29. The fallback module2915-a may be an example of the fallback module 2915 of FIG. 29. Thefallback module 2915-a may include different modules, such acircuit-switched fallback-like module 3826, a cell change order module3827, a service based handover module 3828, and/or a tune away module3829.

The core network 130-g may also include a redirection module 3825 thatmay be utilized to perform redirection procedures of the user equipment115-m from one radio access network 121 to another. For example, theredirection module 3825 may perform a redirection procedure of the userequipment 115-m from RAN 121-i to one of the radio access networks 121,such as RAN 121-j. The core network 130-g may also include aregistration module 3820 to register user equipment 115-m with respectto different RANs 121.

FIG. 39 shows a block diagram of a communications system 3900 that maybe configured for utilizing mobility for wireless communications systemsin accordance with various embodiments. This system 3900 may be anexample of aspects of the system 100 depicted in FIG. 1, systems 200 ofFIG. 2, systems 300 of FIG. 3, and/or system 4200 of FIG. 42. The radioaccess network 121-f may include aspects of a base station 105 and/or acontroller 120 to represent a combined system and/or separate componentsthat may comprise part of a radio access network. The radio accessnetwork 121-f may include antennas 3945, a transceiver module 3950,memory 3970, and a processor module 3965, which each may be incommunication, directly or indirectly, with each other (e.g., over oneor more buses). The transceiver module 3950 may be configured tocommunicate bi-directionally, via the antennas 3945, with the userequipment 115-n, which may be a multi-mode user equipment. Thetransceiver module 3950 (and/or other components of the radio accessnetwork 121-f) may also be configured to communicate bi-directionallywith one or more networks. In some cases, the radio access network 121-fmay communicate with the network 130-h through network communicationsmodule 3975. Radio access network 121-f may be an example of an eNodeBbase station, a Home eNodeB base station, a NodeB base station, and/or aHome NodeB base station. System 3900 may be configured to implementdifferent aspects of the call flows and/or systems as shown in FIGS.30-37 and/or associated description.

Radio access network 121-f may also communicate with base stations 105,such as base station 105-m and base station 105-n. Each of the basestations 105 may communicate with user equipment 115-n using differentwireless communications technologies, such as different Radio AccessTechnologies. In some cases, radio access network 121-f may communicatewith other base stations such as 105-m and/or 105-n utilizing basestation communication module 3920. In some embodiments, base stationcommunication module 3920 may provide an X2 interface within an LTEwireless communication technology to provide communication between someof the base stations 105. In some embodiments, radio access network121-f may communicate with other base stations through network 130-h.

The memory 3970 may include random access memory (RAM) and read-onlymemory (ROM). The memory 3970 may also store computer-readable,computer-executable software code 3971 containing instructions that areconfigured to, when executed, cause the processor module 3965 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 3971 maynot be directly executable by the processor module 3965 but beconfigured to cause the computer, e.g., when compiled and executed, toperform functions described herein.

The processor module 3965 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 3965 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets, and provide indicationsof whether a user is speaking. The processor module 3965 may alsoinclude a speech decoder that may perform a reverse functionality as thespeech encoder.

The transceiver module 3950 may include a modem configured to modulatethe packets and provide the modulated packets to the antennas 3945 fortransmission, and to demodulate packets received from the antennas 3945.While some examples of the radio access network 121-f may include asingle antenna 3945, the radio access network 121-f preferably includesmultiple antennas 3945 for multiple links which may support carrieraggregation. For example, one or more links may be used to support macrocommunications with user equipment 115-n.

According to the architecture of FIG. 39, the radio access network 121-fmay further include a base station communications module 3920. The basestation communications management module 3920 may manage communicationswith other base stations 105. By way of example, the base stationscommunications management module 3920 may be a component of the radioaccess network 121-f in communication with some or all of the othercomponents of the radio access network 121-f via a bus. Alternatively,functionality of the communications management module 3930 may beimplemented as a computer program product, and/or as one or morecontroller elements of the processor module 3965.

The components for radio access network 121-f may be configured toimplement aspects discussed above with respect to device 21900 in FIG.29. The network identification module 2910-b may be an example of thenetwork identification module 2900 of FIG. 29. The fallback module2915-b may be an example of the fallback module 2915 of FIG. 29. Thefallback module 2915-b may include different modules, such acircuit-switched fallback-like module 3926, a cell change order module3927, a service based handover module 3928, and/or a tune away module3929.

The radio access network 121-f may also include a redirection module3930 that may be utilized to perform redirection procedures of the userequipment 115-n from base stations 105 to another. For example, theredirection module 3930 may perform a redirection procedure of the userequipment 115-n from base station 105-m to another base station 105-n.In some embodiments, a handover module 3925 may be utilized to performhandover procedures of the user equipment 115-n from one base station105 to another. For example, the handover module 3925 may perform ahandover procedure of the user equipment 115-n from radio access network121-f to another where normal waveforms are utilized between the userequipment 115-n and one of the base stations and flexible bandwidthwaveforms are utilized between the user equipment and another basestation. A scaling module 3924 may be utilized to scale and/or alterchip rates to generate flexible bandwidth waveforms.

In some embodiments, the transceiver module 3950 in conjunction withantennas 3945, along with other possible components of radio accessnetwork 121-f, may transmit information regarding flexible bandwidthwaveforms and/or scaling factors from the radio access network 121-f tothe user equipment 115-n, to other base stations 105-m/105-n, or corenetwork 130-h. In some embodiments, the transceiver module 3950 inconjunction with antennas 3945, along with other possible components ofradio access network 121-f, may transmit information to the userequipment 115-f, to other base stations 105-m/105-n, or core network130-h, such as flexible bandwidth waveforms and/or scaling factors, suchthat these devices or systems may utilize flexible bandwidth waveforms.

FIG. 40 is a block diagram 4000 of a user equipment 115-o configured formobility in accordance with various embodiments. The user equipment115-o may have any of various configurations, such as personal computers(e.g., laptop computers, netbook computers, tablet computers, etc.),cellular telephones, PDAs, digital video recorders (DVRs), internetappliances, gaming consoles, e-readers, etc. The user equipment 115-omay have an internal power supply (not shown), such as a small battery,to facilitate mobile operation. In some embodiments, the user equipment115-o may be the user equipment 115 of FIG. 1, FIG. 2, FIG. 3, FIG. 38,FIG. 39, and/or FIG. 42, and/or the device 2900 of FIG. 29. The userequipment 115-o may be a multi-mode user equipment. The user equipment115-o may be referred to as a wireless communications device in somecases. User equipment 115-o may be configured to implement differentaspects of the call flows and/or systems as shown in FIGS. 30-37 and/orassociated descriptions.

The user equipment 115-o may include antennas 4040, a transceiver module4050, memory 4080, and a processor module 4070, which each may be incommunication, directly or indirectly, with each other (e.g., via one ormore buses). The transceiver module 4050 is configured to communicatebi-directionally, via the antennas 4040 and/or one or more wired orwireless links, with one or more networks, as described above. Forexample, the transceiver module 4050 may be configured to communicatebi-directionally with base stations 105 of FIG. 1, FIG. 2, FIG. 3,and/or FIG. 42; and/or the radio access networks 121 of FIG. 38 and/orFIG. 39. The transceiver module 4050 may include a modem configured tomodulate the packets and provide the modulated packets to the antennas4040 for transmission, and to demodulate packets received from theantennas 4040. While the user equipment 115-o may include a singleantenna, the user equipment 115-o will typically include multipleantennas 4040 for multiple links.

The memory 4080 may include random access memory (RAM) and read-onlymemory (ROM). The memory 4080 may store computer-readable,computer-executable software code 4085 containing instructions that areconfigured to, when executed, cause the processor module 4070 to performvarious functions described herein (e.g., call processing, databasemanagement, message routing, etc.). Alternatively, the software 4085 maynot be directly executable by the processor module 4070 but beconfigured to cause the computer (e.g., when compiled and executed) toperform functions described herein.

The processor module 4070 may include an intelligent hardware device,e.g., a central processing unit (CPU) such as those made by Intel®Corporation or AMD®, a microcontroller, an application-specificintegrated circuit (ASIC), etc. The processor module 4070 may include aspeech encoder (not shown) configured to receive audio via a microphone,convert the audio into packets (e.g., 20 ms in length) representative ofthe received audio, provide the audio packets, and provide indicationsof whether a user is speaking. The processor module 4070 may alsoinclude a speech decoder that may perform a reverse functionality as thespeech encoder.

According to the architecture of FIG. 40, the user equipment 115-o mayfurther include a communications management module 4060. Thecommunications management module 4060 may manage communications withbase stations. By way of example, the communications management module4060 may be a component of the user equipment 115-o in communicationwith some or all of the other components of the user equipment 115-o viaa bus. Alternatively, functionality of the communications managementmodule 4060 may be implemented as a component of the transceiver module4050, as a computer program product, and/or as one or more controllerelements of the processor module 4070.

The components for user equipment 115-o may be configured to implementaspects discussed above with respect to device 2900 in FIG. 29 and maynot be repeated here for the sake of brevity. The fallback module 2915-cmay be the fallback module 2915 of FIG. 29. User equipment 115-o mayalso include a tune away module 4020.

The user equipment 115-o may also include a spectrum identificationmodule 4015. The spectrum identification module 4015 may be utilized toidentify spectrum available for flexible bandwidth waveforms. In someembodiments, a handover module 4025 may be utilized to perform handoverprocedures of the user equipment 115-o from one base station to another.For example, the handover module 4025 may perform a handover procedureof the user equipment 115-o from one base station to another wherenormal waveforms are utilized between the user equipment 115-o and oneof the base stations and flexible bandwidth waveforms are utilizedbetween the user equipment and another base station. A scaling module4027 may be utilized to scale and/or alter chip rates to generateflexible bandwidth waveforms.

In some embodiments, the transceiver module 4050, in conjunction withantennas 4040, along with other possible components of user equipment115-o, may transmit and/or receive information regarding flexiblebandwidth waveforms and/or scaling factors from the user equipment 115-oto base stations or a core network. In some embodiments, the transceivermodule 4050, in conjunction with antennas 4040, along with otherpossible components of user equipment 115-o, may transmit and/or receiveinformation, such flexible bandwidth waveforms and/or scaling factors,to base stations or a core network such that these devices or systemsmay utilize flexible bandwidth waveforms.

Turning to FIG. 41A, a flow diagram of a method 4100-a for providingmobility in a wireless communications systems in accordance with variousembodiments. Method 4100-a may be implemented utilizing various wirelesscommunications devices and/or systems including, but not limited to: thecore networks 130 of FIG. 1, FIG. 3B, and/or FIG. 38; the user equipment115 of FIG. 1, FIG. 2, FIG. 3, FIG. 38, FIG. 39, FIG. 40, and/or FIG.42; radio access networks 121 of FIG. 3, FIG. 38 and/or FIG. 39; and/ordevice 2900 of FIG. 29. Method 4100-a may implement different aspects ofthe call flows and/or systems as shown in FIGS. 30-37 and/or associateddescriptions.

Communicating over first radio access network, wherein the first radioaccess network utilizes a first flexible bandwidth carrier may occur atblock 4110. Identifying a second radio access network may occur at block4115. The second radio access network may utilize a first bandwidthcarrier. Transitioning from utilizing the first flexible bandwidthcarrier of the first radio access network to utilizing the firstbandwidth carrier of the second radio access network may occur at block4120.

Transitioning from utilizing the first flexible bandwidth carrier of thefirst radio access network to utilizing the first bandwidth carrier ofthe second radio access network may be directed at least in part by acore network. Transitioning from utilizing the first flexible bandwidthcarrier of the first radio access network to utilizing the firstbandwidth carrier of the second radio access network may be directed atleast in part by at least one of the radio access networks. At leasttransitioning from utilizing the first flexible bandwidth carrier of thefirst radio access network to utilizing the first bandwidth carrier ofthe second radio access network or identifying the second radio accessnetwork may relate to a call set-up. The first bandwidth carrier of thesecond radio access network may include a normal bandwidth carrier or asecond flexible bandwidth carrier.

At least transitioning from utilizing the first flexible bandwidthcarrier of the first radio access network to utilizing the firstbandwidth carrier of the second radio access network or identifying thesecond radio access network may relate to circuit-switched voiceservices for a user equipment.

At least transitioning from utilizing the first flexible bandwidthcarrier of the first radio access network to utilizing the firstbandwidth carrier of the second radio access network or identifying thesecond radio access network may include utilizing a circuit-switchedfallback-like procedure. In some cases, an indicator, which may includea flag, may be utilized to signal the use of the circuit-switchedfallback-like procedure. The indicator may utilize new messaging or anextension of existing messaging. In other cases, one of the radio accessnetworks or a core network may determine that the circuit-switchedfallback-like procedure is being utilized with receiving a specificindicator signaling the use of the circuit-switched fallback-likeprocedure. At least transitioning from utilizing the first flexiblebandwidth carrier of the first radio access network to utilizing thefirst bandwidth carrier of the second radio access network oridentifying the second radio access network may include utilizing a cellchange order procedure. At least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing aservice-based handover. At least transitioning from utilizing the firstflexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing aRAN redirection procedure. At least transitioning from utilizing thefirst flexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkor identifying the second radio access network may include utilizing atune away procedure by a user equipment.

Turning to FIG. 41B, a flow diagram of a method 4100-b for providingmobility in a wireless communications systems in accordance with variousembodiments. Method 4100-b may be implemented utilizing various wirelesscommunications devices and/or systems including, but not limited to: thecore networks 130 of FIG. 1, FIG. 3B, and/or FIG. 38; the user equipment115 of FIG. 1, FIG. 2, FIG. 3, FIG. 38, FIG. 39, FIG. 40, and/or FIG.42; radio access networks 121 of FIG. 3, FIG. 38 and/or FIG. 39; and/ordevice 2900 of FIG. 29. Method 4100-b may implement different aspects ofthe call flows and/or systems as shown in FIGS. 30-37 and/or associateddescriptions.

Communicating with a user equipment a flexible bandwidth carrier mayoccur at block 4110-a. Identifying a normal bandwidth carrier may occurat block 4115-a. Transitioning from utilizing the flexible bandwidthcarrier to utilizing the normal bandwidth carrier may occur at block4120-a. Communication with the user equipment over the normal bandwidthcarrier may occur at 4125.

Turning to FIG. 41C, a flow diagram of a method 4100-c for providingmobility in a wireless communications systems in accordance with variousembodiments. Method 4100-c may be implemented utilizing various wirelesscommunications devices and/or systems including, but not limited to: thecore networks 130 of FIG. 1, FIG. 3B, and/or FIG. 38; the user equipment115 of FIG. 1, FIG. 2, FIG. 3, FIG. 38, FIG. 39, FIG. 40, and/or FIG.42; radio access networks 121 of FIG. 3, FIG. 38 and/or FIG. 39; and/ordevice 2900 of FIG. 29. Method 4100-c may implement different aspects ofthe call flows and/or systems as shown in FIGS. 30-37 and/or associateddescriptions. Method 4100-c may include one or more aspects of method4100-a of FIG. 41A and/or method 4100-b of FIG. 41B.

Communicating with a user equipment over first radio access network,wherein the first radio access network utilizes a first flexiblebandwidth carrier, may occur at block 4110-b. At block, a call-set upwith the user equipment that involves a circuit-switched voice servicemay be initiated. Identifying a second radio access network may occur atblock 4115-b. The second radio access network may utilize a firstbandwidth carrier that supports a specific circuit-switched service,such as a CS voice service. At block 4135, it may be determined whetherto redirect the specific circuit-switched service at a core network orat one of the radio access networks. Transitioning from utilizing thefirst flexible bandwidth carrier of the first radio access network toutilizing the first bandwidth carrier of the second radio access networkmay occur at block 4120-b. At block 4140, the specific circuit-switchedservice for the user equipment may be established utilizing the secondbandwidth carrier of the second radio access network.

FIG. 42 is a block diagram of a system 4200 including a base station105-f and a user equipment 115-p in accordance with various embodiments.This system 4200 may be an example of the system 100 of FIG. 1, systems200 of FIG. 2, systems 300 of FIG. 3, system 700 of FIG. 7, system 1100of FIG. 11, system 1300 of FIG. 13, system 2500 of FIG. 25, system 3800of FIG. 38, and/or system 3900 of FIG. 39. The base station 105-f may beequipped with antennas 4234-a through 4234-x, and the user equipment115-p may be equipped with antennas 4252-a through 4252-n. At the basestation 105-f, a transmit processor 4220 may receive data from a datasource. System 4200 may be configured to implement different aspects ofthe call flows and/or systems as shown in FIGS. 4-20 and/or associateddescription.

The transmit processor 4220 may process the data. The transmit processor4220 may also generate reference symbols, and a cell-specific referencesignal. A transmit (TX) MIMO processor 4230 may perform spatialprocessing (e.g., precoding) on data symbols, control symbols, and/orreference symbols, if applicable, and may provide output symbol streamsto the transmit modulators 4232-a through 4232-x. Each modulator 4232may process a respective output symbol stream (e.g., for OFDM, etc.) toobtain an output sample stream. Each modulator 4232 may further process(e.g., convert to analog, amplify, filter, and upconvert) the outputsample stream to obtain a downlink (DL) signal. In one example, DLsignals from modulators 4232-a through 4232-x may be transmitted via theantennas 4234-a through 4234-x, respectively. The transmit processor4220 may receive information from a processor 4240. The processor 4240may be coupled with a memory 4242. The processor 4240 may be configuredto generate flexible bandwidth waveforms through altering a chip rateand/or utilizing a scaling factor. In some embodiments, the processormodule 4240 may be configured for dynamically adapting flexiblebandwidth in accordance with various embodiments. The processor 4240 maydynamically adjust one or more scale factors of the flexible bandwidthsignal associated with transmissions between base station 105-f and userequipment 115-p. These adjustments may be made based on information suchas traffic patterns, interference measurements, etc.

For example, within system 4200, the processor 4240 may configured formobility between flexible bandwidth systems and other bandwidth systems,such as normal bandwidth systems and/or other flexible bandwidthsystems. Processor 4240 may be configured to provide mobility betweendifferent bandwidth systems may facilitate supporting circuit-switchedservices, such as circuit-switched voice services. Processor 4240 may beconfigured to provide for determining flexible bandwidth capabledevices, such as user equipment 115-p. Some embodiments involve corenetwork redirection, where core network 130 may direct the handling ofcircuit-switched services, such as a CS voice service, when a flexiblebandwidth system does not support the CS services. Processor 4240 may beconfigured to provide for radio access network, which may include basestations 105 and/or controller 120, directed and/or determined handlingof CS services, such as CS voice services, when a flexible bandwidthsystem does not support the CS services. Processor 4240 may beconfigured to provide for transitioning or spring forward to a flexiblebandwidth system. Processor 4240 may be configured to provide fortransitioning or fallback from flexible bandwidth systems tonon-flexible bandwidth systems that have no support for some or all CSservices (e.g., CS voice), other flexible bandwidth systems, and/orsystems that natively support CS voice services.

At the user equipment 115-p, the user equipment antennas 4252-a through4252-n may receive the DL signals from the base station 105-f and mayprovide the received signals to the demodulators 4254-a through 4254-n,respectively. Each demodulator 4254 may condition (e.g., filter,amplify, downconvert, and digitize) a respective received signal toobtain input samples. Each demodulator 4254 may further process theinput samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMOdetector 4256 may obtain received symbols from all the demodulators4254-a through 4254-n, perform MIMO detection on the received symbols,if applicable, and provide detected symbols. A receive processor 4258may process (e.g., demodulate, deinterleave, and decode) the detectedsymbols, providing decoded data for the user equipment 115-p to a dataoutput, and provide decoded control information to a processor 4280, ormemory 4282.

On the uplink (UL) or reverse link, at the user equipment 115-p, atransmit processor 4264 may receive and process data from a data source.The transmitter processor 4264 may also generate reference symbols for areference signal. The symbols from the transmit processor 4264 may beprecoded by a transmit MIMO processor 4266, if applicable, furtherprocessed by the demodulators 4254-a through 4254-n (e.g., for SC-FDMA,etc.), and be transmitted to the base station 105-f in accordance withthe transmission parameters received from the base station 105-f. Thetransmit processor 4264 may also be configured to generate flexiblebandwidth waveforms through altering a chip rate and/or utilizing ascaling factor; this may be done dynamically in some cases. The transmitprocessor 4264 may receive information from processor 4280. Theprocessor 4280 may provide for different alignment and/or offsettingprocedures. The processor 4280 may also utilize scaling and/or chip rateinformation to perform measurements on the other subsystems, performhandoffs to the other subsystems, perform reselection, etc. Theprocessor 4280 may invert the effects of time stretching associated withthe use of flexible bandwidth through parameter scaling. At the basestation 105-f, the UL signals from the user equipment 115-p may bereceived by the antennas 4234, processed by the demodulators 4232,detected by a MIMO detector 4236, if applicable, and further processedby a receive processor. The receive processor 4238 may provide decodeddata to a data output and to the processor 4280. In some embodiments,the processor 4280 may be implemented as part of a general processor,the transmit processor 4264, and/or the receiver processor 4258.

In some embodiments, the processor module 4280 may be configured fordynamically adapting flexible bandwidth in accordance with variousembodiments. The processor 4280 may dynamically adjust one or more scalefactors of the flexible bandwidth signal associated with transmissionsbetween base station 105-f and user equipment 115-p. These adjustmentsmay be made based on information such as traffic patterns, interferencemeasurements, etc.

For example, within system 4200, the processor 4280 may configured formobility between flexible bandwidth systems and other bandwidth systems,such as normal bandwidth systems and/or other flexible bandwidthsystems. Processor 4280 may be configured to provide mobility betweendifferent bandwidth systems may facilitate supporting circuit-switchedservices, such as circuit-switched voice services. Processor 4280 may beconfigured to provide for determining flexible bandwidth capabledevices, such as user equipment 115-p. Some embodiments involve corenetwork redirection, where core network 130 may direct the handling ofcircuit-switched services, such as a CS voice service, when a flexiblebandwidth system does not support the CS services. Processor 4280 may beconfigured to provide for radio access network, which may include basestations 105 and/or controller 120, directed and/or determined handlingof CS services, such as CS voice services, when a flexible bandwidthsystem does not support the CS services. Processor 4280 may beconfigured to provide for transitioning or spring forward to a flexiblebandwidth system. Processor 4280 may be configured to provide fortransitioning or fallback from flexible bandwidth systems tonon-flexible bandwidth systems that have no support for some or all CSservices (e.g., CS voice), other flexible bandwidth systems, and/orsystems that natively support CS voice services.

The detailed description set forth above in connection with the appendeddrawings describes exemplary embodiments and does not represent the onlyembodiments that may be implemented or that are within the scope of theclaims. The term “exemplary” used throughout this description means“serving as an example, instance, or illustration,” and not “preferred”or “advantageous over other embodiments.” The detailed descriptionincludes specific details for the purpose of providing an understandingof the described techniques. These techniques, however, may be practicedwithout these specific details. In some instances, well-known structuresand devices are shown in block diagram form in order to avoid obscuringthe concepts of the described embodiments.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a digital signal processor (DSP), anapplication-specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope and spirit of the disclosure and appended claims. For example,due to the nature of software, functions described above can beimplemented using software executed by a processor, hardware, firmware,hardwiring, or combinations of any of these. Features implementingfunctions may also be physically located at various positions, includingbeing distributed such that portions of functions are implemented atdifferent physical locations. Also, as used herein, including in theclaims, “or” as used in a list of items prefaced by “at least one of”indicates a disjunctive list such that, for example, a list of “at leastone of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., Aand B and C).

Computer-readable media includes both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage medium may be anyavailable medium that can be accessed by a general-purpose orspecial-purpose computer. By way of example, and not limitation,computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that can be used to carry or store desiredprogram code means in the form of instructions or data structures andthat can be accessed by a general-purpose or special-purpose computer,or a general-purpose or special-purpose processor. Also, any connectionis properly termed a computer-readable medium. For example, if thesoftware is transmitted from a website, server, or other remote sourceusing a coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave, then the coaxial cable, fiber optic cable, twisted pair,DSL, or wireless technologies such as infrared, radio, and microwave areincluded in the definition of medium. Disk and disc, as used herein,include compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk and blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The previous description of the disclosure is provided to enable aperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Throughout this disclosure the term “example” or“exemplary” indicates an example or instance and does not imply orrequire any preference for the noted example. Thus, the disclosure isnot to be limited to the examples and designs described herein but is tobe accorded the widest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method for providing mobility within wirelesscommunications systems comprising: identifying, at a core network, alack of support for one or more circuit-switched (CS) services on aflexible bandwidth radio access network from a plurality of radio accessnetworks; and redirecting, at the core network, the one or more CSservices for a user equipment from the flexible bandwidth radio accessnetwork to a radio access network that supports the circuit-switchedservice from the plurality of radio access networks.
 2. The method ofclaim 1, further comprising: registering, at the core network, the userequipment over the flexible bandwidth radio access network with respectto at least one packet switched service.
 3. The method of claim 1,further comprising: registering, at the core network, the user equipmentover the flexible bandwidth radio access network with respect to atleast one circuit-switched service.
 4. The method of claim 3, whereinthe at least one circuit-switched service includes a non-voice circuitswitched service.
 5. The method of claim 4, wherein the at least onenon-voice circuit-switched service includes at least SMS or CS data. 6.The method of claim 1, further comprising: receiving, at the corenetwork, a registration request from the user equipment on the flexiblebandwidth radio access network.
 7. The method of claim 1, wherein theone or more CS services includes at least a CS voice service, a Release99 CS voice service, or a CS voice service over one or more datachannels.
 8. The method of claim 1, wherein the user equipment is campedon the flexible bandwidth radio access network.
 9. The method of claim1, wherein the user equipment is currently at least being served by orcamped on a flexible bandwidth carrier that lacks support for a CSservice.
 10. The method of claim 9, wherein the CS service is a CS voiceservice.
 11. The method of claim 1, wherein the circuit-switched servicecomprises a circuit-switched voice service.
 12. The method of claim 1,wherein the core network is aware of the capabilities of the flexiblebandwidth RAN.
 13. The method of claim 1, wherein the flexible bandwidthradio access network is aware that the flexible bandwidth radio accessnetwork lacks support for the circuit-switched service but does notinitiate redirection.
 14. The method of claim 1, wherein the corenetwork is unaware that the CS service is unsupported on the flexiblebandwidth radio access network.
 15. The method of claim 1, wherein thecore network determines that the CS service is unsupported on theflexible bandwidth radio access network.
 16. A wireless communicationssystem configured for mobility, the system comprising: means foridentifying, at a core network, a lack of support for one or morecircuit-switched (CS) services on a flexible bandwidth radio accessnetwork from a plurality of radio access networks; and means forredirecting, at the core network, the one or more CS services for a userequipment from the flexible bandwidth radio access network to a radioaccess network that supports the circuit-switched service from theplurality of radio access networks.
 17. The wireless communicationssystem of claim 16, further comprising: means for registering, at thecore network, the user equipment over the flexible bandwidth radioaccess network with respect to at least one packet switched service. 18.The wireless communications system of claim 16, further comprising:means for registering, at the core network, the user equipment over theflexible bandwidth radio access network with respect to at least onecircuit-switched service.
 19. The wireless communications system ofclaim 16, further comprising: means for receiving, at the core network,a registration request from the user equipment on the flexible bandwidthradio access network.
 20. The wireless communications system of claim16, wherein the user equipment is camped on the flexible bandwidth radioaccess network.
 21. The wireless communications system of claim 16,wherein the user equipment is currently at least being served by orcamped on a flexible bandwidth carrier that lacks support for a CSservice.
 22. The wireless communications system of claim 16, wherein thecircuit-switched service comprises a circuit-switched voice service. 23.The wireless communications system of claim 16, wherein the core networkis aware of the capabilities of the flexible bandwidth radio accessnetwork.
 24. The wireless communications system of claim 16, wherein theflexible bandwidth radio access network is aware that the flexiblebandwidth radio access network lacks support for the circuit-switchedservice but does not initiate redirection.
 25. The wirelesscommunications system of claim 16, wherein the core network is unawarethat the CS service is unsupported on the flexible bandwidth radioaccess network.
 26. The wireless communications system of claim 16,wherein the core network determines that the CS service is unsupportedon the flexible bandwidth radio access network.
 27. A computer programproduct for mobility in a wireless communications system comprising: anon-transitory computer-readable medium comprising: code foridentifying, at a core network, a lack of support for one or morecircuit-switched (CS) services on a flexible bandwidth radio accessnetwork from a plurality of radio access networks; and code forredirecting, at the core network, the one or more CS services for a userequipment from the flexible bandwidth radio access network to a radioaccess network that supports the circuit-switched service from theplurality of radio access networks.
 28. The computer program product ofclaim 27, further comprising: code for registering, at the core network,the user equipment over the flexible bandwidth radio access network withrespect to at least one packet switched service.
 29. The computerprogram product of claim 27, further comprising: code for registering,at the core network, the user equipment over the flexible bandwidthradio access network with respect to at least one circuit-switchedservice.
 30. The computer program product of claim 27, furthercomprising: code for receiving, at the core network, a registrationrequest from the user equipment on the flexible bandwidth radio accessnetwork.
 31. The computer program product of claim 27, wherein the userequipment is camped on the flexible bandwidth radio access network. 32.The computer program product of claim 27, wherein the user equipment iscurrently at least being served by or camped on a flexible bandwidthcarrier that lacks support for a CS service.
 33. The computer programproduct of claim 27, wherein the circuit-switched service comprises acircuit-switched voice service.
 34. The computer program product ofclaim 27, wherein the core network is aware of the capabilities of theflexible bandwidth radio access network.
 35. The computer programproduct of claim 27, wherein the flexible bandwidth radio access networkis aware that the flexible bandwidth radio access network lacks supportfor the circuit-switched service but does not initiate redirection. 36.The computer program product of claim 27, wherein the core network isunaware that the CS service is unsupported on the flexible bandwidthradio access network.
 37. The computer program product of claim 27,wherein the core network determines that the CS service is unsupportedon the flexible bandwidth radio access network.
 38. A wirelesscommunications device configured for mobility in a wirelesscommunications system, the device comprising: at least one processorconfigured to: identify, at a core network, a lack of support for one ormore circuit-switched (CS) services on a flexible bandwidth radio accessnetwork from a plurality of radio access networks; and redirect, by thecore network, the one or more CS services for a user equipment from theflexible bandwidth radio access network to a radio access network thatsupports the circuit-switched service from the plurality of radio accessnetworks.
 39. The wireless communications device of claim 38, whereinthe at least one processor is further configured to: register, at thecore network, the user equipment over the flexible bandwidth radioaccess network with respect to at least one packet switched service. 40.The wireless communications device of claim 38, wherein the at least oneprocessor is further configured to: register, at the core network, theuser equipment over the flexible bandwidth radio access network withrespect to at least one circuit-switched service.
 41. The wirelesscommunications device of claim 38, wherein the at least one processor isfurther configured to: receive, at the core network, a registrationrequest from the user equipment on the flexible bandwidth radio accessnetwork.
 42. The wireless communications device of claim 38, wherein theuser equipment is camped on the flexible bandwidth radio access network.43. The wireless communications device of claim 38, wherein the userequipment is currently at least being served by or camped on a flexiblebandwidth carrier that lacks support for a CS service.
 44. The wirelesscommunications device of claim 38, wherein the circuit-switched servicecomprises a circuit-switched voice service.
 45. The wirelesscommunications device of claim 38, wherein the core network is aware ofthe capabilities of the flexible bandwidth radio access network.
 46. Thewireless communications device of claim 38, wherein the flexiblebandwidth radio access network is aware that the flexible bandwidthradio access network lacks support for the circuit-switched service butdoes not initiate redirection.
 47. The wireless communications device ofclaim 38, wherein the core network is unaware that the CS service isunsupported on the flexible bandwidth radio access network.
 48. Thewireless communications device of claim 38, wherein the core networkdetermines that the CS service is unsupported on the flexible bandwidthradio access network.